Datasets:
Update README.md
Browse files
README.md
CHANGED
@@ -1,3 +1,165 @@
|
|
1 |
-
---
|
2 |
-
license: cdla-sharing-1.0
|
3 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
---
|
2 |
+
license: cdla-sharing-1.0
|
3 |
+
task_categories:
|
4 |
+
- question-answering
|
5 |
+
- table-question-answering
|
6 |
+
language:
|
7 |
+
- en
|
8 |
+
tags:
|
9 |
+
- question-answering
|
10 |
+
- llm
|
11 |
+
- chatbot
|
12 |
+
- hospitality
|
13 |
+
- conversational-ai
|
14 |
+
- generative-ai
|
15 |
+
- natural-language-understanding
|
16 |
+
- fine-tuning
|
17 |
+
pretty_name: >-
|
18 |
+
Bitext - Hospitality Tagged Training Dataset for LLM-based Virtual Assistants
|
19 |
+
size_categories:
|
20 |
+
- 10K<n<100K
|
21 |
+
---
|
22 |
+
# Bitext - Hospitality Tagged Training Dataset for LLM-based Virtual Assistants
|
23 |
+
|
24 |
+
## Overview
|
25 |
+
|
26 |
+
This hybrid synthetic dataset is designed to be used to fine-tune Large Language Models such as GPT, Mistral and OpenELM, and has been generated using our NLP/NLG technology and our automated Data Labeling (DAL) tools. The goal is to demonstrate how Verticalization/Domain Adaptation for the [hospitality] sector can be easily achieved using our two-step approach to LLM Fine-Tuning. An overview of this approach can be found at: [From General-Purpose LLMs to Verticalized Enterprise Models](https://www.bitext.com/blog/general-purpose-models-verticalized-enterprise-genai/)
|
27 |
+
|
28 |
+
The dataset has the following specifications:
|
29 |
+
|
30 |
+
- Use Case: Intent Detection
|
31 |
+
- Vertical: Hospitality
|
32 |
+
- 25 intents assigned to 16 categories
|
33 |
+
- 25000 question/answer pairs, with approximately 1000 per intent
|
34 |
+
- 40 entity/slot types
|
35 |
+
- 10 different types of language generation tags
|
36 |
+
|
37 |
+
The categories and intents are derived from Bitext's extensive experience across various industry-specific datasets, ensuring the relevance and applicability across diverse contexts.
|
38 |
+
|
39 |
+
## Dataset Token Count
|
40 |
+
|
41 |
+
The dataset contains a total of 1.87 million tokens across 'instruction' and 'response' columns. This extensive corpus is crucial for training sophisticated LLMs that can perform a variety of functions including conversational AI, question answering, and virtual assistant tasks in the hospitality domain.
|
42 |
+
|
43 |
+
## Fields of the Dataset
|
44 |
+
|
45 |
+
Each entry in the dataset comprises the following fields:
|
46 |
+
|
47 |
+
- tags
|
48 |
+
- instruction: a user request from the Hospitality domain
|
49 |
+
- category: the high-level semantic category for the intent
|
50 |
+
- intent: the specific intent corresponding to the user instruction
|
51 |
+
- response: an example of an expected response from the virtual assistant
|
52 |
+
|
53 |
+
## Categories and Intents
|
54 |
+
|
55 |
+
The dataset covers a wide range of hospitality-related categories and intents, which are:
|
56 |
+
|
57 |
+
- **BILLING**: invoices
|
58 |
+
- **CANCELLATION_FEES**: cancellation_fees
|
59 |
+
- **CHECK_IN**: check_in
|
60 |
+
- **CHECK_OUT**: check_out
|
61 |
+
- **CONTACT**: customer_service, human_agent
|
62 |
+
- **EVENT**: host_event
|
63 |
+
- **FEEDBACK**: file_complaint, leave_review
|
64 |
+
- **HOTEL**: book_hotel, cancel_hotel_reservation, change_hotel_reservation, check_hotel_facilities, check_hotel_offers, check_hotel_prices, check_hotel_reservation, search_hotel
|
65 |
+
- **LUGGAGE**: store_luggage
|
66 |
+
- **MENU**: check_menu
|
67 |
+
- **NIGHT**: add_night
|
68 |
+
- **PARKING_SPACE**: book_parking_space
|
69 |
+
- **PETS**: bring_pets
|
70 |
+
- **POINTS**: redeem_points
|
71 |
+
- **REFUND**: get_refund
|
72 |
+
- **SHUTTLE_SERVICE**: shuttle_service
|
73 |
+
|
74 |
+
## Entities
|
75 |
+
|
76 |
+
The entities covered by the dataset include:
|
77 |
+
|
78 |
+
- **{{WEBSITE_URL}}**, common with most intents.
|
79 |
+
- **{{SPEAK_WITH_HUMAN_AGENT_OPTION}}**, featured in intents like human_agent.
|
80 |
+
- **{{CHECK_OUT_OPTION}}**, associated with intents like check_out.
|
81 |
+
- **{{CHARGE_TYPE}}**, relevant to intents such as cancellation_fees.
|
82 |
+
- **{{DESTINATION_CITY}}**, featured in intents like book_hotel, change_hotel_reservation.
|
83 |
+
|
84 |
+
This comprehensive list of entities ensures that the dataset is well-equipped to train models that are highly adept at understanding and processing a wide range of hospitality-related queries and tasks.
|
85 |
+
|
86 |
+
## Language Generation Tags
|
87 |
+
|
88 |
+
The dataset includes tags indicative of various language variations and styles adapted for Hospitality, enhancing the robustness and versatility of models trained on this data. These tags categorize the utterances into different registers such as colloquial, formal, or containing specific hospitality jargon, ensuring that the trained models can understand and generate a range of conversational styles appropriate for different customer interactions in the hospitality sector.
|
89 |
+
|
90 |
+
## Language Generation Tags
|
91 |
+
|
92 |
+
The dataset includes tags that reflect various language variations and styles, crucial for creating adaptable and responsive conversational AI models within the hospitality sector. These tags help in understanding and generating appropriate responses based on the linguistic context and user interaction style.
|
93 |
+
|
94 |
+
### Tags for Lexical variation
|
95 |
+
|
96 |
+
- **M - Morphological variation**: Adjusts for inflectional and derivational forms.
|
97 |
+
- Example: "is my account active", "is my account activated"
|
98 |
+
- **L - Semantic variations**: Handles synonyms, use of hyphens, and compounding.
|
99 |
+
- Example: “what's my balance date", “what's my billing date”
|
100 |
+
|
101 |
+
### Tags for Syntactic structure variation
|
102 |
+
|
103 |
+
- **B - Basic syntactic structure**: Simple, direct commands or statements.
|
104 |
+
- Example: "activate my card", "I need to check my balance"
|
105 |
+
- **I - Interrogative structure**: Structuring sentences in the form of questions.
|
106 |
+
- Example: “can you show my balance?”, “how do I transfer money?”
|
107 |
+
- **C - Coordinated syntactic structure**: Complex sentences coordinating multiple ideas or tasks.
|
108 |
+
- Example: “I want to transfer money and check my balance, what should I do?”
|
109 |
+
- **N - Negation**: Expressing denial or contradiction.
|
110 |
+
- Example: "I do not wish to proceed with this transaction, how can I stop it?"
|
111 |
+
|
112 |
+
### Tags for language register variations
|
113 |
+
|
114 |
+
- **P - Politeness variation**: Polite forms often used in customer service.
|
115 |
+
- Example: “could you please help me check my account balance?”
|
116 |
+
- **Q - Colloquial variation**: Informal language that might be used in casual customer interactions.
|
117 |
+
- Example: "can u tell me my balance?"
|
118 |
+
- **W - Offensive language**: Handling potentially offensive language which might occasionally appear in frustrated customer interactions.
|
119 |
+
- Example: “I’m upset with these charges, this is ridiculous!”
|
120 |
+
|
121 |
+
### Tags for stylistic variations
|
122 |
+
|
123 |
+
- **K - Keyword mode**: Responses focused on keywords.
|
124 |
+
- Example: "balance check", "account status"
|
125 |
+
- **E - Use of abbreviations**: Common abbreviations.
|
126 |
+
- Example: “acct for account”, “trans for transaction”
|
127 |
+
- **Z - Errors and Typos**: Includes common misspellings or typographical errors found in customer inputs.
|
128 |
+
- Example: “how can I chek my balance”
|
129 |
+
|
130 |
+
### Other tags not in use in this Dataset
|
131 |
+
|
132 |
+
- **D - Indirect speech**: Expressing commands or requests indirectly.
|
133 |
+
- Example: “I was wondering if you could show me my last transaction.”
|
134 |
+
- **G - Regional variations**: Adjustments for regional language differences.
|
135 |
+
- Example: American vs British English: "checking account" vs "current account"
|
136 |
+
- **R - Respect structures - Language-dependent variations**: Formality levels appropriate in different languages.
|
137 |
+
- Example: Using “vous” in French for formal addressing instead of “tu.”
|
138 |
+
- **Y - Code switching**: Switching between languages or dialects within the same conversation.
|
139 |
+
- Example: “Can you help me with my cuenta, please?”
|
140 |
+
|
141 |
+
These tags not only aid in training models for a wide range of customer interactions but also ensure that the models are culturally and linguistically sensitive, enhancing the customer experience in hospitality environments.
|
142 |
+
|
143 |
+
## License
|
144 |
+
|
145 |
+
The `Bitext-hospitality-llm-chatbot-training-dataset` is released under the **Community Data License Agreement (CDLA) Sharing 1.0**. This license facilitates broad sharing and collaboration while ensuring that the freedom to use, share, modify, and utilize the data remains intact for all users.
|
146 |
+
|
147 |
+
### Key Aspects of CDLA-Sharing 1.0
|
148 |
+
|
149 |
+
- **Attribution and ShareAlike**: Users must attribute the dataset and continue to share derivatives under the same license.
|
150 |
+
- **Non-Exclusivity**: The license is non-exclusive, allowing multiple users to utilize the data simultaneously.
|
151 |
+
- **Irrevocability**: Except in cases of material non-compliance, rights under this license are irrevocable.
|
152 |
+
- **No Warranty**: The dataset is provided without warranties regarding its accuracy, completeness, or fitness for a particular purpose.
|
153 |
+
- **Limitation of Liability**: Both users and data providers limit their liability for damages arising from the use of the dataset.
|
154 |
+
|
155 |
+
### Usage Under CDLA-Sharing 1.0
|
156 |
+
|
157 |
+
By using the `Bitext-hospitality-llm-chatbot-training-dataset`, you agree to adhere to the terms set forth in the CDLA-Sharing 1.0. It is essential to ensure that any publications or distributions of the data, or derivatives thereof, maintain attribution to the original data providers and are distributed under the same or compatible terms of this agreement.
|
158 |
+
|
159 |
+
For a detailed understanding of the license, refer to the [official CDLA-Sharing 1.0 documentation](https://cdla.dev/sharing-1-0/).
|
160 |
+
|
161 |
+
This license supports the open sharing and collaborative improvement of datasets within the AI and data science community, making it particularly suited for projects aimed at developing and enhancing AI technologies in the hospitality sector.
|
162 |
+
|
163 |
+
---
|
164 |
+
|
165 |
+
(c) Bitext Innovations, 2024
|