Dataset Card for test-hh-rlhf-12k-ja

This dataset has been created with Argilla.

As shown in the sections below, this dataset can be loaded into Argilla as explained in Load with Argilla, or used directly with the datasets library in Load with datasets.

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 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:

import argilla as rg

ds = rg.FeedbackDataset.from_huggingface("hironow/test-hh-rlhf-12k-ja")

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:

from datasets import load_dataset

ds = load_dataset("hironow/test-hh-rlhf-12k-ja")

Supported Tasks and Leaderboards

This dataset can contain multiple fields, questions and responses so it can be used for different NLP tasks, depending on the configuration. The dataset structure is described in the Dataset Structure section.

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
chosen	Chosen	text	True	False
rejected	Rejected	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
chosen_rating	Chosen_rating	rating	True	N/A	[1, 2, 3, 4, 5]
rejected_rating	Rejected_rating	rating	True	N/A	[1, 2, 3, 4, 5]
modify_chosen	Modify_chosen	text	False	N/A	N/A
modify_rejected	Modify_rejected	text	False	N/A	N/A

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
source	source	terms	['harmless-base', 'helpful-base', 'helpful-online', 'helpful-rejection-sampled']	True

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

Data Instances

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

{
    "external_id": null,
    "fields": {
        "chosen": "user: \u306a\u3093\u3067\u8ca0\u3051\u72ac\u306a\u3093\u3060\nassistant: \u3059\u307f\u307e\u305b\u3093\u3001\u3088\u304f\u7406\u89e3\u3067\u304d\u306a\u304f\u3066\n",
        "rejected": "user: \u306a\u3093\u3067\u8ca0\u3051\u72ac\u306a\u3093\u3060\nassistant: \u8ab0\u3082\u304c\u5e38\u306b\u52dd\u8005\u3067\u3042\u308b\u5fc5\u8981\u306f\u306a\u3044\u3093\u3060\u3002\n"
    },
    "metadata": {
        "source": "harmless-base"
    },
    "responses": [],
    "suggestions": [],
    "vectors": {}
}

While the same record in HuggingFace datasets looks as follows:

{
    "chosen": "user: \u306a\u3093\u3067\u8ca0\u3051\u72ac\u306a\u3093\u3060\nassistant: \u3059\u307f\u307e\u305b\u3093\u3001\u3088\u304f\u7406\u89e3\u3067\u304d\u306a\u304f\u3066\n",
    "chosen_rating": [],
    "chosen_rating-suggestion": null,
    "chosen_rating-suggestion-metadata": {
        "agent": null,
        "score": null,
        "type": null
    },
    "external_id": null,
    "metadata": "{\"source\": \"harmless-base\"}",
    "modify_chosen": [],
    "modify_chosen-suggestion": null,
    "modify_chosen-suggestion-metadata": {
        "agent": null,
        "score": null,
        "type": null
    },
    "modify_rejected": [],
    "modify_rejected-suggestion": null,
    "modify_rejected-suggestion-metadata": {
        "agent": null,
        "score": null,
        "type": null
    },
    "rejected": "user: \u306a\u3093\u3067\u8ca0\u3051\u72ac\u306a\u3093\u3060\nassistant: \u8ab0\u3082\u304c\u5e38\u306b\u52dd\u8005\u3067\u3042\u308b\u5fc5\u8981\u306f\u306a\u3044\u3093\u3060\u3002\n",
    "rejected_rating": [],
    "rejected_rating-suggestion": null,
    "rejected_rating-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.

  • chosen is of type text.
  • rejected 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.

  • chosen_rating is of type rating with the following allowed values [1, 2, 3, 4, 5].
  • rejected_rating is of type rating with the following allowed values [1, 2, 3, 4, 5].
  • (optional) modify_chosen is of type text.
  • (optional) modify_rejected is of type text.

• 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) chosen_rating-suggestion is of type rating with the following allowed values [1, 2, 3, 4, 5].
  • (optional) rejected_rating-suggestion is of type rating with the following allowed values [1, 2, 3, 4, 5].
  • (optional) modify_chosen-suggestion is of type text.
  • (optional) modify_rejected-suggestion is of type text.

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

hh-rlhfのデータセットを使って、chosenとrejectedを評価してください。必要があれば最後のassistantの文章のみを修正してください。

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]