README.md

---
size_categories: n<1K
tags:
- rlfh
- argilla
- human-feedback
---

# Dataset Card for argilla-dataset

This dataset has been created with [Argilla](https://docs.argilla.io).

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).

## Dataset Description

- **Homepage:** https://argilla.io
- **Repository:** https://github.com/argilla-io/argilla
- **Paper:** 
- **Leaderboard:** 
- **Point of Contact:** 

### Dataset Summary

This dataset contains:

* A dataset configuration file conforming to the Argilla dataset format named `argilla.yaml`. This configuration file will be used to configure the dataset when using the `FeedbackDataset.from_huggingface` method in Argilla.

* 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`.

* The [annotation guidelines](#annotation-guidelines) that have been used for building and curating the dataset, if they've been defined in Argilla.

### Load with Argilla

To load with Argilla, you'll just need to install Argilla as `pip install argilla --upgrade` and then use the following code:

```python
import argilla as rg

ds = rg.FeedbackDataset.from_huggingface("arkamaldeen/argilla-dataset")
```

### Load with `datasets`

To load this dataset with `datasets`, you'll just need to install `datasets` as `pip install datasets --upgrade` and then use the following code:

```python
from datasets import load_dataset

ds = load_dataset("arkamaldeen/argilla-dataset")
```

### Supported Tasks and Leaderboards

This dataset can contain [multiple fields, questions and responses](https://docs.argilla.io/en/latest/conceptual_guides/data_model.html#feedback-dataset) 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).

There are no leaderboards associated with this dataset.

### Languages

[More Information Needed]

## Dataset Structure

### Data in Argilla

The dataset is created in Argilla with: **fields**, **questions**, **suggestions**, **metadata**, **vectors**, and **guidelines**.

The **fields** are the dataset records themselves, for the moment just text fields are supported. These are the ones that will be used to provide responses to the questions.

| Field Name | Title | Type | Required | Markdown |
| ---------- | ----- | ---- | -------- | -------- |
| text | Text | text | True | False |


The **questions** are the questions that will be asked to the annotators. They can be of different types, such as rating, text, label_selection, multi_label_selection, or ranking.

| Question Name | Title | Type | Required | Description | Values/Labels |
| ------------- | ----- | ---- | -------- | ----------- | ------------- |
| validate | Validate | label_selection | True | N/A | ['select', 'unselect'] |


The **suggestions** are human or machine generated recommendations for each question to assist the annotator during the annotation process, so those are always linked to the existing questions, and named appending "-suggestion" and "-suggestion-metadata" to those, containing the value/s of the suggestion and its metadata, respectively. So on, the possible values are the same as in the table above, but the column name is appended with "-suggestion" and the metadata is appended with "-suggestion-metadata".

The **metadata** is a dictionary that can be used to provide additional information about the dataset record. This can be useful to provide additional context to the annotators, or to provide additional information about the dataset record itself. For example, you can use this to provide a link to the original source of the dataset record, or to provide additional information about the dataset record itself, such as the author, the date, or the source. The metadata is always optional, and can be potentially linked to the `metadata_properties` defined in the dataset configuration file in `argilla.yaml`.



| Metadata Name | Title | Type | Values | Visible for Annotators |
| ------------- | ----- | ---- | ------ | ---------------------- |


The **guidelines**, are optional as well, and are just a plain string that can be used to provide instructions to the annotators. Find those in the [annotation guidelines](#annotation-guidelines) section.

### Data Instances

An example of a dataset instance in Argilla looks as follows:

```json
{
    "external_id": null,
    "fields": {
        "text": "\u0b13\u0b21\u0b3f\u0b36\u0b3e\u0b30 \u0b2a\u0b3e\u0b30\u0b2e\u0b4d\u0b2a\u0b3e\u0b30\u0b3f\u0b15 \u0b36\u0b2c\u0b26\u0b3e\u0b39 \u0b30\u0b40\u0b24\u0b3f\u0b28\u0b40\u0b24\u0b3f \u0b0f\u0b2c\u0b02 \u0b05\u0b28\u0b4d\u0b24\u0b3f\u0b2e\u0b38\u0b02\u0b38\u0b4d\u0b15\u0b3e\u0b30"
    },
    "metadata": {},
    "responses": [
        {
            "status": "submitted",
            "user_id": "0cd57185-cddd-408b-b469-2f0198f7c5e1",
            "values": {
                "validate": {
                    "value": "unselect"
                }
            }
        }
    ],
    "suggestions": [],
    "vectors": {}
}
```

While the same record in HuggingFace `datasets` looks as follows:

```json
{
    "external_id": null,
    "metadata": "{}",
    "text": "\u0b13\u0b21\u0b3f\u0b36\u0b3e\u0b30 \u0b2a\u0b3e\u0b30\u0b2e\u0b4d\u0b2a\u0b3e\u0b30\u0b3f\u0b15 \u0b36\u0b2c\u0b26\u0b3e\u0b39 \u0b30\u0b40\u0b24\u0b3f\u0b28\u0b40\u0b24\u0b3f \u0b0f\u0b2c\u0b02 \u0b05\u0b28\u0b4d\u0b24\u0b3f\u0b2e\u0b38\u0b02\u0b38\u0b4d\u0b15\u0b3e\u0b30",
    "validate": [
        {
            "status": "submitted",
            "user_id": "0cd57185-cddd-408b-b469-2f0198f7c5e1",
            "value": "unselect"
        }
    ],
    "validate-suggestion": null,
    "validate-suggestion-metadata": {
        "agent": null,
        "score": null,
        "type": null
    }
}
```

### Data Fields

Among the dataset fields, we differentiate between the following:

* **Fields:** These are the dataset records themselves, for the moment just text fields are supported. These are the ones that will be used to provide responses to the questions.
    
    * **text** is of type `text`.

* **Questions:** These are the questions that will be asked to the annotators. They can be of different types, such as `RatingQuestion`, `TextQuestion`, `LabelQuestion`, `MultiLabelQuestion`, and `RankingQuestion`.
    
    * **validate** is of type `label_selection` with the following allowed values ['select', 'unselect'].

* **Suggestions:** As of Argilla 1.13.0, the suggestions have been included to provide the annotators with suggestions to ease or assist during the annotation process. Suggestions are linked to the existing questions, are always optional, and contain not just the suggestion itself, but also the metadata linked to it, if applicable.
    
    * (optional) **validate-suggestion** is of type `label_selection` with the following allowed values ['select', 'unselect'].



Additionally, we also have two more fields that are optional and are the following:

* **metadata:** This is an optional field that can be used to provide additional information about the dataset record. This can be useful to provide additional context to the annotators, or to provide additional information about the dataset record itself. For example, you can use this to provide a link to the original source of the dataset record, or to provide additional information about the dataset record itself, such as the author, the date, or the source. The metadata is always optional, and can be potentially linked to the `metadata_properties` defined in the dataset configuration file in `argilla.yaml`.
* **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.

### Data Splits

The dataset contains a single split, which is `train`.

## Dataset Creation

### Curation Rationale

[More Information Needed]

### Source Data

#### Initial Data Collection and Normalization

[More Information Needed]

#### Who are the source language producers?

[More Information Needed]

### Annotations

#### Annotation guidelines

[More Information Needed]

#### Annotation process

[More Information Needed]

#### Who are the annotators?

[More Information Needed]

### Personal and Sensitive Information

[More Information Needed]

## Considerations for Using the Data

### Social Impact of Dataset

[More Information Needed]

### Discussion of Biases

[More Information Needed]

### Other Known Limitations

[More Information Needed]

## Additional Information

### Dataset Curators

[More Information Needed]

### Licensing Information

[More Information Needed]

### Citation Information

[More Information Needed]

### Contributions

[More Information Needed]