tanikina commited on
Commit
d347c61
1 Parent(s): 5363383

add dataset card

Browse files
Files changed (1) hide show
  1. README.md +207 -0
README.md ADDED
@@ -0,0 +1,207 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ ---
2
+ task_categories:
3
+ - text-classification
4
+ language:
5
+ - de
6
+ pretty_name: Intent Classification for Robot Assisted Disaster Response
7
+ size_categories:
8
+ - 100K<n<1M
9
+ ---
10
+ # Dataset Card for "Intent Classification for Robot Assisted Disaster Response"
11
+
12
+ <!-- Provide a quick summary of the dataset. -->
13
+
14
+ This dataset consists of conversations recorded during the training sessions in the emergency response domain.
15
+ The conversations are typically between several operators controlling the robots, a team leader and a mission commander.
16
+ The data have been transcribed and annotated during the following projects: [TRADR](http://www.tradr-project.eu/) and [ADRZ](https://rettungsrobotik.de/home).
17
+ The dialogues are split into turns and each turn is annotated with a speaker and intent.
18
+
19
+ ## Dataset Details
20
+
21
+ ### Dataset Description
22
+
23
+ <!-- Provide a longer summary of what this dataset is. -->
24
+
25
+
26
+
27
+ - **Curated by:** DFKI, [Talking Robots Group at MLT](https://www.dfki.de/en/web/research/research-departments/multilinguality-and-language-technology/tr-team)
28
+ <!-- - **Funded by [optional]:** [More Information Needed] -->
29
+ <!-- - **Shared by [optional]:** [More Information Needed] -->
30
+ - **Language(s) (NLP):** German
31
+ - **License:** [More Information Needed]
32
+
33
+ <!-- ### Dataset Sources [optional] -->
34
+
35
+ <!-- Provide the basic links for the dataset. -->
36
+
37
+ <!-- - **Repository:** [More Information Needed] -->
38
+ <!-- - **Paper [optional]:** [More Information Needed] -->
39
+ <!-- - **Demo [optional]:** [More Information Needed] -->
40
+
41
+ <!-- ## Uses -->
42
+
43
+ <!-- Address questions around how the dataset is intended to be used. -->
44
+
45
+ <!-- ### Direct Use -->
46
+
47
+ <!-- This section describes suitable use cases for the dataset. -->
48
+
49
+ <!-- [More Information Needed] -->
50
+
51
+ <!-- ### Out-of-Scope Use -->
52
+
53
+ <!-- This section addresses misuse, malicious use, and uses that the dataset will not work well for. -->
54
+
55
+ <!-- [More Information Needed] -->
56
+
57
+ ## Dataset Structure
58
+
59
+ <!-- This section provides a description of the dataset fields, and additional information about the dataset structure such as criteria used to create the splits, relationships between data points, etc. -->
60
+
61
+ ### Data Instances
62
+
63
+ ```
64
+ {
65
+ 'id': '1236',
66
+ 'speaker': 'UAV',
67
+ 'text': 'wir haben einmal den Akku gewechselt, bis jetzt noch kein Rauch festzustellen ...',
68
+ 'label': 2
69
+ }
70
+ ```
71
+
72
+ ### Data Fields
73
+
74
+ ```
75
+ id: the id of the dialogue turn, an `int` feature
76
+ speaker: the speaker of the turn, a `string` feature
77
+ text: the utterance of the turn, a `string` feature
78
+ label: the label of the turn, an `int` feature
79
+ ```
80
+
81
+ ### Data Splits
82
+
83
+ This dataset contains 3525 dialogue turns in total. The data are split as follows: 2610 turns for training, 310 for development and 605 for test. The data represent a continuous conversation, i.e., the previous id refers to the previous turn in the dialogue.
84
+
85
+ ### Label Description and Statistics
86
+
87
+ | label | meaning | train | percentage | example |
88
+ | --- | --- | --- | --- | --- |
89
+ | 0 | disconfirm | 35 | 1.3% | `Ist negativ, noch nicht.` |
90
+ | 1 | order | 216 | 8.3% | `Für Sie Erkundungsauftrag: Gesamtüberblick über die Einsatzstelle. Kommen.` |
91
+ | 2 | info_provide | 979 | 37.5% | `Ich verlasse das Erdgeschoss und gehe ins erste Obergeschoss.` |
92
+ | 3 | info_request | 238 | 9.1% | `Frage: Erkundungsergebnis aus der östlichen Seite des Gebäudes, kommen.` |
93
+ | 4 | call | 487 | 18.7% | `RobLW an Zugführer, kommen.` |
94
+ | 5 | call_response | 370 | 14.2% | `Ja, hier ist Zugführer, kommen.` |
95
+ | 6 | other | 43 | 1.7% | `Einen Augenblick, ich melde mich gleich.` |
96
+ | 7 | confirm | 242 | 9.3% | `Ein Lagebild von oben, komplette Lage, und ein Lagebild zwischen den beiden Türen, verstanden.` |
97
+ ## Dataset Creation
98
+ ### Curation Rationale
99
+ The dataset is based on the recordings from the emergency response domain that use radio communication protocol. The goal of the conversation is to coordinate rescue operations in a robot-assisted disaster response.
100
+ ### Source Data
101
+ The data are based on human-human communication in robot-assisted disaster response. The dialogues are task-oriented, focused on collaborative execution of a mission by a team that uses robots to to explore some area, find hazardous materials, locate fires, damage or victims.
102
+ #### Data Collection and Processing
103
+ The initial audio recordings were collected during the [TRADR](http://www.tradr-project.eu/) and [ADRZ](https://rettungsrobotik.de/home) projects, transcribed and annotated by the [Talking Robots Group, DFKI](https://www.dfki.de/en/web/research/research-departments/multilinguality-and-language-technology/tr-team)
104
+ <!--#### Who are the source data producers?-->
105
+ <!-- This section describes the people or systems who originally created the data. It should also include self-reported demographic or identity information for the source data creators if this information is available. -->
106
+ ### Annotations
107
+ The annotations include dialogue intents relevant for communication in the emergency response domain: `call`, `call_response`, `info_request`, `info_provide`, `confirm`, `disconfirm`, `order` and `other`.
108
+
109
+ Note the interpretation of the intent depends on the context. E.g., the following examples illustrate how very similar responses ("Warten", "Wait") are annotated differently depending on the previous turn:
110
+
111
+ ```
112
+ (1) disconfirm
113
+ - Können wir weitermachen? (Shall we continue?)
114
+ - Warten. (Wait.)
115
+ (2) confirm
116
+ - Hast du die Möglichkeit, das Fass näher zu identifizieren, was da drin ist? (Can you inspect the barrel closer to identify what is inside?)
117
+ - Ja, warten. (Yes, wait.)
118
+ (3) order
119
+ - Werde aber jetzt auch mal die rückwärtige Seite des Fasses erkunden. (I will inspect now the back side of the barrel.)
120
+ - UGV 1, damit warten. (UGV 1, wait.)
121
+ (4) other (pausing to check)
122
+ - Frage: kommen meine Fotos an? (Question: do you receive my photos?)
123
+ - Warten. (Wait.)
124
+ ```
125
+
126
+ #### Annotation process
127
+
128
+ <!-- This section describes the annotation process such as annotation tools used in the process, the amount of data annotated, annotation guidelines provided to the annotators, interannotator statistics, annotation validation, etc. -->
129
+
130
+ The recordings were manually transcribed and annotated with emergency response intents. There are 3525 dialogue turns in total with 6.3 tokens per turn on average.
131
+
132
+ #### Who are the annotators?
133
+
134
+ All annotations were done by the research assistants of the [Talking Robots Group, DFKI](https://www.dfki.de/en/web/research/research-departments/multilinguality-and-language-technology/tr-team)
135
+
136
+ #### Personal and Sensitive Information
137
+
138
+ <!-- State whether the dataset contains data that might be considered personal, sensitive, or private (e.g., data that reveals addresses, uniquely identifiable names or aliases, racial or ethnic origins, sexual orientations, religious beliefs, political opinions, financial or health data, etc.). If efforts were made to anonymize the data, describe the anonymization process. -->
139
+ The dataset does not include any real names, addresses or other personal information. The recordings were done during training sessions with simulations of the emergency situation.
140
+
141
+ ## Bias, Risks, and Limitations
142
+
143
+ <!-- This section is meant to convey both technical and sociotechnical limitations. -->
144
+
145
+ The dataset covers only a subset of possible emergency situations, focusing mainly on fire, building collapse and chemical leakage. It does not address many other situations, e.g., traffic accidents, floods or explosions.
146
+
147
+ <!--### Recommendations -->
148
+
149
+ <!-- This section is meant to convey recommendations with respect to the bias, risk, and technical limitations. -->
150
+
151
+ <!-- Users should be made aware of the risks, biases and limitations of the dataset. More information needed for further recommendations. -->
152
+
153
+ ## Citation
154
+
155
+ <!-- If there is a paper or blog post introducing the dataset, the APA and Bibtex information for that should go in this section. -->
156
+ Part of this dataset has been introduced in the following paper. However, the current version includes more annotated turns due to additional data collection.
157
+
158
+ **BibTeX:**
159
+
160
+ ```
161
+ @inproceedings{anikina-2023-towards,
162
+ title = "Towards Efficient Dialogue Processing in the Emergency Response Domain",
163
+ author = "Anikina, Tatiana",
164
+ editor = "Padmakumar, Vishakh and
165
+ Vallejo, Gisela and
166
+ Fu, Yao",
167
+ booktitle = "Proceedings of the 61st Annual Meeting of the Association for Computational Linguistics (Volume 4: Student Research Workshop)",
168
+ month = jul,
169
+ year = "2023",
170
+ address = "Toronto, Canada",
171
+ publisher = "Association for Computational Linguistics",
172
+ url = "https://aclanthology.org/2023.acl-srw.31",
173
+ doi = "10.18653/v1/2023.acl-srw.31",
174
+ pages = "212--225",
175
+ abstract = "In this paper we describe the task of adapting NLP models to dialogue processing in the emergency response domain. Our goal is to provide a recipe for building a system that performs dialogue act classification and domain-specific slot tagging while being efficient, flexible and robust. We show that adapter models Pfeiffer et al. (2020) perform well in the emergency response domain and benefit from additional dialogue context and speaker information. Comparing adapters to standard fine-tuned Transformer models we show that they achieve competitive results and can easily accommodate new tasks without significant memory increase since the base model can be shared between the adapters specializing on different tasks. We also address the problem of scarce annotations in the emergency response domain and evaluate different data augmentation techniques in a low-resource setting.",
176
+ }
177
+ ```
178
+
179
+ **APA:**
180
+
181
+ ```
182
+ Anikina, T. (2023). Towards Efficient Dialogue Processing in the Emergency Response Domain. Annual Meeting of the Association for Computational Linguistics.
183
+ ```
184
+
185
+ ## Glossary
186
+
187
+ Abbrevations used for the speakers:
188
+
189
+ UGV: Unmanned Ground Vehicle
190
+
191
+ UAV: Unmanned Aerial Vehicle
192
+
193
+ MC: Mission Commander
194
+
195
+ TL: Team Leader
196
+
197
+ RobLW: Robotikleitwagen (robotic lead vehicle)
198
+
199
+ ZF: Zugführer (fire brigade commander)
200
+
201
+ GF: Gruppenführer (group leader)
202
+
203
+ ELW: Einsatzleitwagen (emergency command vehicle)
204
+
205
+ GW-DUK: Gerätewagen-Daten-und-Kommunikation (vehicle for transporting robots and equipment)
206
+
207
+ <!-- If relevant, include terms and calculations in this section that can help readers understand the dataset or dataset card. -->