Datasets:
Commit
•
57b72e9
1
Parent(s):
703671c
Upload README.md with huggingface_hub
Browse files
README.md
CHANGED
@@ -1,57 +1,315 @@
|
|
1 |
---
|
2 |
-
|
3 |
-
|
4 |
-
|
5 |
-
|
6 |
-
|
7 |
-
dtype: string
|
8 |
-
id: field
|
9 |
-
- name: instruction
|
10 |
-
dtype: string
|
11 |
-
id: field
|
12 |
-
- name: context
|
13 |
-
dtype: string
|
14 |
-
id: field
|
15 |
-
- name: response
|
16 |
-
dtype: string
|
17 |
-
id: field
|
18 |
-
- name: final-instruction
|
19 |
-
sequence:
|
20 |
-
- name: user_id
|
21 |
-
dtype: string
|
22 |
-
- name: value
|
23 |
-
dtype: string
|
24 |
-
- name: status
|
25 |
-
dtype: string
|
26 |
-
id: question
|
27 |
-
- name: final-context
|
28 |
-
sequence:
|
29 |
-
- name: user_id
|
30 |
-
dtype: string
|
31 |
-
- name: value
|
32 |
-
dtype: string
|
33 |
-
- name: status
|
34 |
-
dtype: string
|
35 |
-
id: question
|
36 |
-
- name: final-response
|
37 |
-
sequence:
|
38 |
-
- name: user_id
|
39 |
-
dtype: string
|
40 |
-
- name: value
|
41 |
-
dtype: string
|
42 |
-
- name: status
|
43 |
-
dtype: string
|
44 |
-
id: question
|
45 |
-
- name: external_id
|
46 |
-
dtype: string
|
47 |
-
id: external_id
|
48 |
-
splits:
|
49 |
-
- name: train
|
50 |
-
num_bytes: 12647374
|
51 |
-
num_examples: 15015
|
52 |
-
download_size: 7720859
|
53 |
-
dataset_size: 12647374
|
54 |
---
|
55 |
-
# Dataset Card for "dolly_tutorial"
|
56 |
|
57 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
---
|
2 |
+
size_categories: 10K<n<100K
|
3 |
+
tags:
|
4 |
+
- rlfh
|
5 |
+
- argilla
|
6 |
+
- human-feedback
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
7 |
---
|
|
|
8 |
|
9 |
+
# Dataset Card for dolly_tutorial
|
10 |
+
|
11 |
+
This dataset has been created with [Argilla](https://docs.argilla.io).
|
12 |
+
|
13 |
+
As shown in the sections below, this dataset can be loaded into Argilla as explained in [Load with Argilla](#load-with-argilla), or used directly with the `datasets` library in [Load with `datasets`](#load-with-datasets).
|
14 |
+
|
15 |
+
## Dataset Description
|
16 |
+
|
17 |
+
- **Homepage:** https://argilla.io
|
18 |
+
- **Repository:** https://github.com/argilla-io/argilla
|
19 |
+
- **Paper:**
|
20 |
+
- **Leaderboard:**
|
21 |
+
- **Point of Contact:**
|
22 |
+
|
23 |
+
### Dataset Summary
|
24 |
+
|
25 |
+
This dataset contains:
|
26 |
+
|
27 |
+
* A dataset configuration file conforming to the Argilla dataset format named `argilla.cfg`. This configuration file will be used to configure the dataset when using the `FeedbackDataset.from_huggingface` method in Argilla.
|
28 |
+
|
29 |
+
* Dataset records in a format compatible with HuggingFace `datasets`. These records will be loaded automatically when using `FeedbackDataset.from_huggingface` and can be loaded independently using the `datasets` library via `load_dataset`.
|
30 |
+
|
31 |
+
* The [annotation guidelines](#annotation-guidelines) that have been used for building and curating the dataset, if they've been defined in Argilla.
|
32 |
+
|
33 |
+
### Load with Argilla
|
34 |
+
|
35 |
+
To load with Argilla, you'll just need to install Argilla as `pip install argilla --upgrade` and then use the following code:
|
36 |
+
|
37 |
+
```python
|
38 |
+
import argilla as rg
|
39 |
+
|
40 |
+
ds = rg.FeedbackDataset.from_huggingface("nataliaElv/dolly_tutorial")
|
41 |
+
```
|
42 |
+
|
43 |
+
### Load with `datasets`
|
44 |
+
|
45 |
+
To load this dataset with `datasets`, you'll just need to install `datasets` as `pip install datasets --upgrade` and then use the following code:
|
46 |
+
|
47 |
+
```python
|
48 |
+
from datasets import load_dataset
|
49 |
+
|
50 |
+
ds = load_dataset("nataliaElv/dolly_tutorial")
|
51 |
+
```
|
52 |
+
|
53 |
+
### Supported Tasks and Leaderboards
|
54 |
+
|
55 |
+
This dataset can contain [multiple fields, questions and responses](https://docs.argilla.io/en/latest/guides/llms/conceptual_guides/data_model.html) so it can be used for different NLP tasks, depending on the configuration. The dataset structure is described in the [Dataset Structure section](#dataset-structure).
|
56 |
+
|
57 |
+
There are no leaderboards associated with this dataset.
|
58 |
+
|
59 |
+
### Languages
|
60 |
+
|
61 |
+
[More Information Needed]
|
62 |
+
|
63 |
+
## Dataset Structure
|
64 |
+
|
65 |
+
### Data in Argilla
|
66 |
+
|
67 |
+
The dataset is created in Argilla with: **fields**, **questions**, and **guidelines**.
|
68 |
+
|
69 |
+
The **fields** are the dataset records themselves, for the moment just text fields are suppported. These are the ones that will be used to provide responses to the questions.
|
70 |
+
|
71 |
+
| Field Name | Title | Type | Required | Markdown |
|
72 |
+
| ---------- | ----- | ---- | -------- | -------- |
|
73 |
+
| category | Task category | TextField | True | False |
|
74 |
+
| instruction | Instruction | TextField | True | False |
|
75 |
+
| context | Input | TextField | True | False |
|
76 |
+
| response | Response | TextField | True | False |
|
77 |
+
|
78 |
+
|
79 |
+
The **questions** are the questions that will be asked to the annotators. They can be of different types, such as rating, text, single choice, or multiple choice.
|
80 |
+
|
81 |
+
| Question Name | Title | Type | Required | Description | Values/Labels |
|
82 |
+
| ------------- | ----- | ---- | -------- | ----------- | ------------- |
|
83 |
+
| final-instruction | Final Instruction: | TextQuestion | True | Write the final version of the instruction, making sure that it matches the task category. If the original instruction is ok, copy and paste it here. | N/A |
|
84 |
+
| final-context | Final Input: | TextQuestion | True | Write the final version of the input, making sure that it makes sense with the task category. If the original input is ok, copy and paste it here. Leave this question empty in the case of these task categories: open / general Q&A, brainstorming, creative writing. | N/A |
|
85 |
+
| final-response | Final Response: | TextQuestion | True | Write the final version of the response, making sure that it matches the task category and makes sense for the instruction (and input) provided. If the original response is ok, copy and paste it here. Make sure that the grammar and orthography are correct. | N/A |
|
86 |
+
|
87 |
+
|
88 |
+
Finally, the **guidelines** are just a plain string that can be used to provide instructions to the annotators. Find those in the [annotation guidelines](#annotation-guidelines) section.
|
89 |
+
|
90 |
+
### Data Instances
|
91 |
+
|
92 |
+
An example of a dataset instance in Argilla looks as follows:
|
93 |
+
|
94 |
+
```json
|
95 |
+
{
|
96 |
+
"external_id": "0",
|
97 |
+
"fields": {
|
98 |
+
"category": "closed_qa",
|
99 |
+
"context": "Virgin Australia, the trading name of Virgin Australia Airlines Pty Ltd, is an Australian-based airline. It is the largest airline by fleet size to use the Virgin brand. It commenced services on 31 August 2000 as Virgin Blue, with two aircraft on a single route. It suddenly found itself as a major airline in Australia\u0027s domestic market after the collapse of Ansett Australia in September 2001. The airline has since grown to directly serve 32 cities in Australia, from hubs in Brisbane, Melbourne and Sydney.",
|
100 |
+
"instruction": "When did Virgin Australia start operating?",
|
101 |
+
"response": "Virgin Australia commenced services on 31 August 2000 as Virgin Blue, with two aircraft on a single route."
|
102 |
+
},
|
103 |
+
"metadata": null,
|
104 |
+
"responses": [
|
105 |
+
{
|
106 |
+
"status": "submitted",
|
107 |
+
"user_id": "dc9c373f-c589-4845-b7e8-890520ca7d43",
|
108 |
+
"values": {
|
109 |
+
"final-context": {
|
110 |
+
"value": "Virgin Australia, the trading name of Virgin Australia Airlines Pty Ltd, is an Australian-based airline. It is the largest airline by fleet size to use the Virgin brand. It commenced services on 31 August 2000 as Virgin Blue, with two aircraft on a single route. It suddenly found itself as a major airline in Australia\u0027s domestic market after the collapse of Ansett Australia in September 2001. The airline has since grown to directly serve 32 cities in Australia, from hubs in Brisbane, Melbourne and Sydney."
|
111 |
+
},
|
112 |
+
"final-instruction": {
|
113 |
+
"value": "When did Virgin Australia start operating?"
|
114 |
+
},
|
115 |
+
"final-response": {
|
116 |
+
"value": "Virgin Australia commenced services on 31 August 2000 as Virgin Blue."
|
117 |
+
}
|
118 |
+
}
|
119 |
+
}
|
120 |
+
]
|
121 |
+
}
|
122 |
+
```
|
123 |
+
|
124 |
+
While the same record in HuggingFace `datasets` looks as follows:
|
125 |
+
|
126 |
+
```json
|
127 |
+
{
|
128 |
+
"category": "closed_qa",
|
129 |
+
"context": "Virgin Australia, the trading name of Virgin Australia Airlines Pty Ltd, is an Australian-based airline. It is the largest airline by fleet size to use the Virgin brand. It commenced services on 31 August 2000 as Virgin Blue, with two aircraft on a single route. It suddenly found itself as a major airline in Australia\u0027s domestic market after the collapse of Ansett Australia in September 2001. The airline has since grown to directly serve 32 cities in Australia, from hubs in Brisbane, Melbourne and Sydney.",
|
130 |
+
"external_id": "0",
|
131 |
+
"final-context": {
|
132 |
+
"status": [
|
133 |
+
"submitted"
|
134 |
+
],
|
135 |
+
"user_id": [
|
136 |
+
"dc9c373f-c589-4845-b7e8-890520ca7d43"
|
137 |
+
],
|
138 |
+
"value": [
|
139 |
+
"Virgin Australia, the trading name of Virgin Australia Airlines Pty Ltd, is an Australian-based airline. It is the largest airline by fleet size to use the Virgin brand. It commenced services on 31 August 2000 as Virgin Blue, with two aircraft on a single route. It suddenly found itself as a major airline in Australia\u0027s domestic market after the collapse of Ansett Australia in September 2001. The airline has since grown to directly serve 32 cities in Australia, from hubs in Brisbane, Melbourne and Sydney."
|
140 |
+
]
|
141 |
+
},
|
142 |
+
"final-instruction": {
|
143 |
+
"status": [
|
144 |
+
"submitted"
|
145 |
+
],
|
146 |
+
"user_id": [
|
147 |
+
"dc9c373f-c589-4845-b7e8-890520ca7d43"
|
148 |
+
],
|
149 |
+
"value": [
|
150 |
+
"When did Virgin Australia start operating?"
|
151 |
+
]
|
152 |
+
},
|
153 |
+
"final-response": {
|
154 |
+
"status": [
|
155 |
+
"submitted"
|
156 |
+
],
|
157 |
+
"user_id": [
|
158 |
+
"dc9c373f-c589-4845-b7e8-890520ca7d43"
|
159 |
+
],
|
160 |
+
"value": [
|
161 |
+
"Virgin Australia commenced services on 31 August 2000 as Virgin Blue."
|
162 |
+
]
|
163 |
+
},
|
164 |
+
"instruction": "When did Virgin Australia start operating?",
|
165 |
+
"metadata": null,
|
166 |
+
"response": "Virgin Australia commenced services on 31 August 2000 as Virgin Blue, with two aircraft on a single route."
|
167 |
+
}
|
168 |
+
```
|
169 |
+
|
170 |
+
### Data Fields
|
171 |
+
|
172 |
+
Among the dataset fields, we differentiate between the following:
|
173 |
+
|
174 |
+
* **Fields:** These are the dataset records themselves, for the moment just text fields are suppported. These are the ones that will be used to provide responses to the questions.
|
175 |
+
|
176 |
+
* **category** is of type `TextField`.
|
177 |
+
* **instruction** is of type `TextField`.
|
178 |
+
* (optional) **context** is of type `TextField`.
|
179 |
+
* **response** is of type `TextField`.
|
180 |
+
|
181 |
+
* **Questions:** These are the questions that will be asked to the annotators. They can be of different types, such as rating, text, single choice, or multiple choice.
|
182 |
+
|
183 |
+
* **final-instruction** is of type `TextQuestion`, and description "Write the final version of the instruction, making sure that it matches the task category. If the original instruction is ok, copy and paste it here.".
|
184 |
+
* (optional) **final-context** is of type `TextQuestion`, and description "Write the final version of the input, making sure that it makes sense with the task category. If the original input is ok, copy and paste it here. Leave this question empty in the case of these task categories: open / general Q&A, brainstorming, creative writing.".
|
185 |
+
* **final-response** is of type `TextQuestion`, and description "Write the final version of the response, making sure that it matches the task category and makes sense for the instruction (and input) provided. If the original response is ok, copy and paste it here. Make sure that the grammar and orthography are correct.".
|
186 |
+
|
187 |
+
Additionally, we also have one more field which is optional and is the following:
|
188 |
+
|
189 |
+
* **external_id:** This is an optional field that can be used to provide an external ID for the dataset record. This can be useful if you want to link the dataset record to an external resource, such as a database or a file.
|
190 |
+
|
191 |
+
### Data Splits
|
192 |
+
|
193 |
+
The dataset contains a single split, which is `train`.
|
194 |
+
|
195 |
+
## Dataset Creation
|
196 |
+
|
197 |
+
### Curation Rationale
|
198 |
+
|
199 |
+
[More Information Needed]
|
200 |
+
|
201 |
+
### Source Data
|
202 |
+
|
203 |
+
#### Initial Data Collection and Normalization
|
204 |
+
|
205 |
+
[More Information Needed]
|
206 |
+
|
207 |
+
#### Who are the source language producers?
|
208 |
+
|
209 |
+
[More Information Needed]
|
210 |
+
|
211 |
+
### Annotations
|
212 |
+
|
213 |
+
#### Annotation guidelines
|
214 |
+
|
215 |
+
|
216 |
+
# Introduction
|
217 |
+
In this dataset, you will find a collection of records that show a task category, an instruction, an input and a response. The aim of the project is to correct the instructions, inputs and responses to make sure they are of the highest quality and that they match the task category that they belong to. All three texts should be clear and include real information.
|
218 |
+
|
219 |
+
# Task categories
|
220 |
+
Instructions are classified according to 7 possible task categories. Please, read and understand these categories because they will change the way the instruction and input are formulated. The definitions are based on those made by [Databricks](https://www.databricks.com/blog/2023/04/12/dolly-first-open-commercially-viable-instruction-tuned-llm).
|
221 |
+
|
222 |
+
## Open / General Q&A
|
223 |
+
Here you will find an open question, for instance, “Why do people like comedy movies?” or “What is the capital of France?”. In some cases, there’s not a correct answer, and in others, it requires drawing on knowledge of the world at large. This type of task shouldn’t have an input.
|
224 |
+
|
225 |
+
## Closed Q&A
|
226 |
+
These are questions that can be answered using only the information contained in a passage of reference text. For instance, given a paragraph from Wikipedia on the atom, one might ask, “What is the ratio between protons and neutrons in the nucleus?”. In this case, the task should have an instruction (the question), an input (the reference text) and a response.
|
227 |
+
|
228 |
+
## Information extraction
|
229 |
+
In this task, the instruction will ask to extract entities or other factual information from a passage. In this case, the task should have an instruction (the question), an input (the reference text) and a response.
|
230 |
+
|
231 |
+
## Summarization
|
232 |
+
Instructions of this kind of task will ask to summarize a passage. The passage should be in the input. The response should be a summarized version of the passage.
|
233 |
+
|
234 |
+
## Brainstorming
|
235 |
+
Brainstorming instructions should ask for open-ended ideation and an associated list of possible options. For instance, “What are some fun activities I can do with my friends this weekend?”.
|
236 |
+
|
237 |
+
## Classification
|
238 |
+
Instructions of this type should ask to make judgments about class membership (e.g. are the items in a list animals, minerals or vegetables) or to judge the properties of a short passage of text, such as the sentiment of a movie review. The item(s) to be classified should appear in the input field.
|
239 |
+
|
240 |
+
## Creative writing
|
241 |
+
Instructions of this class include things like writing a poem or a love letter.
|
242 |
+
|
243 |
+
|
244 |
+
# Questionnaire
|
245 |
+
To curate the dataset, you will need to provide and answer to the questions below. Please, follow the pointers below to answer each question accordingly.
|
246 |
+
|
247 |
+
If you are not sure about a record and you prefer not to provide a response, click Discard.
|
248 |
+
|
249 |
+
## 1. Final instruction:
|
250 |
+
|
251 |
+
- The final version of the instruction field. You may copy it using the copy icon in the instruction field.
|
252 |
+
- Leave it as it is if it's ok or apply any necessary corrections.
|
253 |
+
- Remember to change the instruction if it doesn't represent well the task category of the record.
|
254 |
+
- Instructions can contain grammar and orthography errors as long as they are clear.
|
255 |
+
|
256 |
+
## 2. Final input:
|
257 |
+
|
258 |
+
- The final version of the instruction field. You may copy it using the copy icon in the input field.
|
259 |
+
- Leave it as it is if it's ok or apply any necessary corrections.
|
260 |
+
- Remember to add an input to the tasks that need one: closed Q&A, information extraction, summarization and classification.
|
261 |
+
- This question should be blank whenever the task doesn’t need one: open / general Q&A, brainstorming, creative writing.
|
262 |
+
- Inputs can contain grammar and orthography errors as long as they are clear.
|
263 |
+
|
264 |
+
## 3. Final response:
|
265 |
+
- The final version of the response field.
|
266 |
+
- You may copy it using the copy icon in the response field.
|
267 |
+
- Leave it as it is if it's ok or apply any necessary corrections.
|
268 |
+
- Check that the response makes sense given all the fields above and that it is as complete and concise as possible.
|
269 |
+
- Responses should have their grammar and orthography checked and correct at all times.
|
270 |
+
|
271 |
+
|
272 |
+
|
273 |
+
#### Annotation process
|
274 |
+
|
275 |
+
[More Information Needed]
|
276 |
+
|
277 |
+
#### Who are the annotators?
|
278 |
+
|
279 |
+
[More Information Needed]
|
280 |
+
|
281 |
+
### Personal and Sensitive Information
|
282 |
+
|
283 |
+
[More Information Needed]
|
284 |
+
|
285 |
+
## Considerations for Using the Data
|
286 |
+
|
287 |
+
### Social Impact of Dataset
|
288 |
+
|
289 |
+
[More Information Needed]
|
290 |
+
|
291 |
+
### Discussion of Biases
|
292 |
+
|
293 |
+
[More Information Needed]
|
294 |
+
|
295 |
+
### Other Known Limitations
|
296 |
+
|
297 |
+
[More Information Needed]
|
298 |
+
|
299 |
+
## Additional Information
|
300 |
+
|
301 |
+
### Dataset Curators
|
302 |
+
|
303 |
+
[More Information Needed]
|
304 |
+
|
305 |
+
### Licensing Information
|
306 |
+
|
307 |
+
[More Information Needed]
|
308 |
+
|
309 |
+
### Citation Information
|
310 |
+
|
311 |
+
[More Information Needed]
|
312 |
+
|
313 |
+
### Contributions
|
314 |
+
|
315 |
+
[More Information Needed]
|