evaluate 0 0 0

wflying/instruction-following-rl-66k

published by @wflying

Alignment dataset tracked in the /datasets sub-catalog.

Lifetime downloads
169
Last 30 days
22
Likes
-
Size
81.7 MB
Created on HF
2026-08-11
Age
2 months ago

Description

Instruction Following RL 66K

Dataset overview

instruction-following-rl-66k is an English training dataset for instruction-following reinforcement learning (RL/RLVR), containing 66,418 examples. It is derived primarily from AllenAI's IF_multi_constraints_upto5, whose instructions contain up to five verifiable constraints drawn from IFEval and IFBench-Train.

Each record is first validated for its JSON, prompt, and metadata structure. A predefined… See the full description on the dataset page: https://huggingface.co/datasets/wflying/instruction-following-rl-66k.

Tags

task_categories:text-generationsource_datasets:allenai/IF_multi_constraints_upto5language:enlicense:odc-bysize_categories:10K<n<100Kregion:usinstruction-followingreinforcement-learningrlvrverifiable-constraintsifevalifbench

README current version from Hugging Face


pretty_name: Instruction Following RL 66K
language:

  • en
    license: odc-by
    task_categories:
  • text-generation
    size_categories:
  • 10K<n<100K
    source_datasets:
  • allenai/IF_multi_constraints_upto5
    tags:
  • instruction-following
  • reinforcement-learning
  • rlvr
  • verifiable-constraints
  • ifeval
  • ifbench
    configs:
  • config_name: default
    data_files:
    • split: train
      path: instruction-following-rl-66k.jsonl

Instruction Following RL 66K

Dataset overview

instruction-following-rl-66k is an English training dataset for instruction-following reinforcement learning (RL/RLVR), containing 66,418 examples. It is derived primarily from AllenAI's IF_multi_constraints_upto5, whose instructions contain up to five verifiable constraints drawn from IFEval and IFBench-Train.

Each record is first validated for its JSON, prompt, and metadata structure. A predefined instruction-ID-to-constraint-checker mapping is then used to verify that every instruction ID has a corresponding checker and that the kwargs, checker-generated natural-language constraint description, and prompt are mutually consistent. The processing subsequently removes known mismatches between prompt descriptions and checker behavior, invalid copy-span boundaries, deterministic cross-constraint conflicts, and unstable targets that would require randomized default values to repair. Finally, records are deduplicated using the SHA-256 hash of the normalized prompt.

Dataset statistics

Item Value
Split train
Examples 66,418
JSONL file size 85,620,970 bytes (approximately 81.65 MiB)
Data type if
Unique instruction IDs 51
Constraints per example 1–5
Prompt length in characters min 35; median 638; P95 1,975; max 10,174
num_tokens min 19; median 158; P95 523; max 2,048

Distribution by number of constraints:

Constraints per example Examples Share
1 13,428 20.22%
2 17,914 26.97%
3 17,798 26.80%
4 12,736 19.18%
5 4,542 6.84%

Data format

Each line is a JSON object with the following fields:

  • prompt: A list containing a single user message in the form [{"role": "user", "content": ...}].
  • label: An empty-string placeholder. Compliance is determined from the verifiable constraints stored in metadata; no supervised reference answer is provided.
  • metadata.instruction_id_list: The list of instruction/checker IDs to validate.
  • metadata.instruction_kwargs: A list of parameter dictionaries aligned one-to-one with instruction_id_list; checkers without parameters may use null.
  • metadata.num_tokens: A precomputed token count. The tokenizer used to produce this value is not recorded in the released file.
  • metadata.data_type: if for every example.

Illustrative example:

{
  "prompt": [
    {
      "role": "user",
      "content": "<task followed by one to five verifiable constraints>"
    }
  ],
  "label": "",
  "metadata": {
    "instruction_id_list": ["<checker-id-1>", "<checker-id-2>"],
    "instruction_kwargs": [{"<arg>": "<value>"}, null],
    "num_tokens": 128,
    "data_type": "if"
  }
}

Data processing

The dataset undergoes strict semantic validation and prompt-level deduplication:

  1. Validate the structure and required non-empty values of the JSON record, prompt, metadata, instruction IDs, and kwargs.
  2. Verify that every instruction ID maps to a defined constraint checker.
  3. Confirm that each checker accepts the supplied kwargs keys and values as-is, rejecting invalid parameters that depend on randomized defaults for repair.
  4. Reconstruct the natural-language constraint description and verify that it agrees with both the prompt text and kwargs.
  5. Remove known mismatches between prompt descriptions and checker behavior, invalid copy-span boundaries, and deterministic cross-constraint conflicts.
  6. Deduplicate records by the SHA-256 hash of the normalized prompt and write the output atomically through a temporary file.

Loading the dataset

from datasets import load_dataset

dataset = load_dataset(
    "wflying/instruction-following-rl-66k",
    split="train",
    streaming=True,
)

sample = next(iter(dataset))
print(sample["prompt"])
print(sample["metadata"]["instruction_id_list"])

License and responsible use

The upstream dataset is licensed under ODC-BY-1.0. This dataset retains the same odc-by license metadata. Users should attribute the upstream dataset and its authors and comply with the Allen Institute for AI Responsible Use Guidelines. The upstream Dataset Card additionally notes that the dataset may contain generated data subject to separate terms of use from third-party model providers; users are responsible for reviewing and complying with all applicable terms.

Sources and citation

Please cite the upstream work:

@misc{pyatkin2025generalizing,
  title={Generalizing Verifiable Instruction Following},
  author={Valentina Pyatkin and Saumya Malik and Victoria Graf and Hamish Ivison and Shengyi Huang and Pradeep Dasigi and Nathan Lambert and Hannaneh Hajishirzi},
  year={2025},
  eprint={TODO},
  archivePrefix={arXiv},
  primaryClass={cs.CL}
}

README history 8 revisions

Every night we snapshot the README of every dataset in the catalog. When the SHA changes we archive the new version and diff it against the last. This is the evolving thought record of the alignment-data field: what the author decided to say about the corpus, and how that framing shifted over time.

  1. 2026-08-12Translate dataset card to English304c8b55.4 KB
    Loading...
  2. 2026-08-11Update README.mde89711e4.9 KB
    Loading...
  3. 2026-08-11Clarify constraint-validation terminologydb196116.3 KB
    Loading...
  4. 2026-08-11Describe data processing without local implementation references0b767a66.2 KB
    Loading...
  5. 2026-08-11Document streaming loader for dynamic JSON kwargs6f605d26.1 KB
    Loading...
  6. 2026-08-11Add dataset cardd77cc135.7 KB
    Loading...
  7. 2026-08-11Upload processed instruction-following RL dataset03adcad0 B
    Loading...
  8. 2026-08-11initial commitd2642580 B
    Loading...

Used by abliterated models none yet

No abliterated models in our catalog have declared this dataset in their YAML metadata yet. This can mean the dataset is used but not declared, is used outside abliteration workflows, or is new. The link will populate automatically as models are indexed.

Related datasets same stage · evaluate

Read further

Metadata

License
odc-by

Repository

Download the dataset

0

Copy any of these snippets into your notebook or terminal. All three fetch directly from Hugging Face using your own credentials.

Recommended: datasets library (Python)
from datasets import load_dataset
ds = load_dataset("wflying/instruction-following-rl-66k")
Raw snapshot (Python)
from huggingface_hub import snapshot_download
snapshot_download(repo_id="wflying/instruction-following-rl-66k", repo_type="dataset")
git clone (requires git-lfs)
git clone https://huggingface.co/datasets/wflying/instruction-following-rl-66k
Catalog is the map. Apps are the tools.

Run models on your own machine, not in the cloud.

Every model page has an "Open in Abliteration" button that hands the model directly to the first-party desktop client, at the quantization your rig can actually run. No API keys, no subscription, no prompt leakage.

Open in Abliteration