evaluate 0 0 0

haritzpuerto/ifeval-lrm

published by @haritzpuerto

Alignment dataset tracked in the /datasets sub-catalog.

Lifetime downloads
433
Last 30 days
20
Likes
-
Size
105 KB
Created on HF
2026-02-25
Age
7 months ago

Description

IFEval Dataset Card

Dataset Description

IFEval is an instruction-following evaluation benchmark consisting of verifiable natural language instructions. Each example specifies one or more constraints that a model must satisfy in its output (e.g., include/exclude phrases, follow a format, respect length or style constraints). In this project, IFEval is used to evaluate both:

instruction following in the reasoning trace (RT), and

instruction following in the final… See the full description on the dataset page: https://huggingface.co/datasets/haritzpuerto/ifeval-lrm.

Tags

language:enlicense:apache-2.0size_categories:n<1Kformat:parquetmodality:textlibrary:datasetslibrary:pandaslibrary:polarslibrary:mlcroissantarxiv:2602.24210arxiv:2311.07911region:us

README current version from Hugging Face


dataset_info:
features:

  • name: key
    dtype: int64
  • name: prompt
    dtype: string
  • name: instruction_id_list
    list: string
  • name: kwargs
    list:
    • name: num_highlights
      dtype: int64
    • name: relation
      dtype: string
    • name: num_words
      dtype: int64
    • name: num_placeholders
      dtype: int64
    • name: prompt_to_repeat
      dtype: string
    • name: num_bullets
      dtype: int64
    • name: section_spliter
      dtype: string
    • name: num_sections
      dtype: int64
    • name: capital_relation
      dtype: string
    • name: capital_frequency
      dtype: int64
    • name: keywords
      list: string
    • name: num_paragraphs
      dtype: int64
    • name: language
      dtype: string
    • name: let_relation
      dtype: string
    • name: letter
      dtype: string
    • name: let_frequency
      dtype: int64
    • name: end_phrase
      dtype: string
    • name: forbidden_words
      list: string
    • name: keyword
      dtype: string
    • name: frequency
      dtype: int64
    • name: num_sentences
      dtype: int64
    • name: postscript_marker
      dtype: string
    • name: first_word
      dtype: string
    • name: nth_paragraph
      dtype: int64
      splits:
  • name: test
    num_bytes: 344197
    num_examples: 541
    download_size: 99799
    dataset_size: 344197
    configs:
  • config_name: default
    data_files:
    • split: test
      path: data/test-*
      license: apache-2.0
      language:
  • en
    size_categories:
  • n<1K

IFEval Dataset Card

Dataset Description

IFEval is an instruction-following evaluation benchmark consisting of verifiable natural language instructions. Each example specifies one or more constraints that a model must satisfy in its output (e.g., include/exclude phrases, follow a format, respect length or style constraints). In this project, IFEval is used to evaluate both:

  • instruction following in the reasoning trace (RT), and
  • instruction following in the final answer (FA).

The benchmark provides automatic, rule-based checks so that compliance can be measured without human annotation.

Intended Use

  • Primary use: Evaluate how well language and reasoning models follow explicit instructions under objective, automatically checkable criteria.
  • This repository’s use: Measure instruction-following performance of controllable reasoning models in both their RTs and FAs.

The dataset is intended only for research and benchmarking and not for deployment in user-facing applications as-is.

Dataset Structure

  • Total size: 541 instructions
  • Splits: only test

Each instance conceptually contains:

  • key: id of the data point
  • prompt The user prompt. We have added an instruction at the end stating that the instructions applies to both the reasoning traces and final answers.
  • instruction_id_list / metadata: machine-readable specification of constraints used by the evaluation scripts.
  • kwargs: information needed by the evaluation script to verify whether constraints are met.

Tasks and Evaluation

  • Main task: Instruction following.
  • Evaluation metric: Instruction-level loose-accuracy, as defined in the original IFEval publication. A prediction is considered correct if it satisfies the verifiable constraints associated with the instruction.
  • In this work:
    • RTs and FAs are evaluated separately with the same loose-accuracy metric to obtain IF-RT and IF-FA scores.

Data Source

IFEval was introduced as an automatic benchmark for instruction following in LLMs. For details on construction, examples, and official evaluation scripts, please refer to the original IFEval paper and repository.

License

  • License: Apache 2.0

Known Limitations and Considerations

  • The benchmark focuses on objective, verifiable instructions and may not capture more nuanced forms of instruction following (e.g., subtle style preferences, conversational alignment).
  • All instructions are in English, so the dataset does not directly measure multilingual instruction-following capabilities.
  • Since the test set is relatively small (540 examples), fine-grained comparisons between very similar systems should be interpreted with care.

Citation

If you use this dataset in your work, please cite the original IFEval paper and this repository’s paper:


@misc{puerto2026leakythoughtsprivatereasoning,
      title={From Leaky Thoughts to Private Reasoning: Controlling What LRMs Say to Themselves}, 
      author={Haritz Puerto and Haonan Li and Xudong Han and Timothy Baldwin and Iryna Gurevych},
      year={2026},
      eprint={2602.24210},
      archivePrefix={arXiv},
      primaryClass={cs.CL},
      url={https://arxiv.org/abs/2602.24210}, 
}

@misc{zhou2023instructionfollowingevaluationlargelanguage,
      title={Instruction-Following Evaluation for Large Language Models}, 
      author={Jeffrey Zhou and Tianjian Lu and Swaroop Mishra and Siddhartha Brahma and Sujoy Basu and Yi Luan and Denny Zhou and Le Hou},
      year={2023},
      eprint={2311.07911},
      archivePrefix={arXiv},
      primaryClass={cs.CL},
      url={https://arxiv.org/abs/2311.07911}, 
}

README history 5 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-09Update README.md04f24635.1 KB
    Loading...
  2. 2026-03-02Update README.md69c37d75.1 KB
    Loading...
  3. 2026-02-26Update README.md257b1f74.7 KB
    Loading...
  4. 2026-02-25Upload datasetb1474631.4 KB
    Loading...
  5. 2026-02-25initial commitd373ee20 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.

Community discussions 1 thread · 1 open · 1 comments

Threads posted by the community on Hugging Face: bug reports, questions about usage, pull requests on the README, license clarifications. Click any thread to expand and read the full conversation inline. Newest first.

  1. 2026-03-02PRAdd link to paper, code and specify task categoriesopen1 💬#1
    Loading...

Related datasets same stage · evaluate

Read further

Metadata

License
apache-2.0

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("haritzpuerto/ifeval-lrm")
Raw snapshot (Python)
from huggingface_hub import snapshot_download
snapshot_download(repo_id="haritzpuerto/ifeval-lrm", repo_type="dataset")
git clone (requires git-lfs)
git clone https://huggingface.co/datasets/haritzpuerto/ifeval-lrm
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