evaluate 0 0 0

hungbenjamin402/IF-multi-constraints-upto5-LFM2.5-prompts

published by @hungbenjamin402

Alignment dataset tracked in the /datasets sub-catalog.

Lifetime downloads
118
Last 30 days
45
Likes
-
Size
77.1 MB
Created on HF
2026-08-20
Age
2 months ago

Description

IF_multi_constraints_upto5 → LFM2.5 prompt format (for RLVR / rejection sampling / DPO)

A derivative of allenai/IF_multi_constraints_upto5 (odc-by)

normalized for fine-tuning Liquid AI LFM2 / LFM2.5 models, whose native tool-call format is Pythonic:

<|im_start|>assistant

<|tool_call_start|>[get_weather(location='Paris, France', unit='celsius')]<|tool_call_end|><|im_end|>

Prompt-only rows (prompt_only = true): Tulu-SFT instructions with up to 5 verifiable constraints from IFEval… See the full description on the dataset page: https://huggingface.co/datasets/hungbenjamin402/IF-multi-constraints-upto5-LFM2.5-prompts.

Tags

task_categories:text-generationsource_datasets:allenai/IF_multi_constraints_upto5language:enlicense:odc-bysize_categories:10K<n<100Kformat:parquetmodality:tabularmodality:textlibrary:datasetslibrary:dasklibrary:polarslibrary:mlcroissantregion:usinstruction-followingifevalifbenchrlvrlfm2lfm2.5prompts

README current version from Hugging Face


license: odc-by
language:

  • en
    task_categories:
  • text-generation
    tags:
  • instruction-following
  • ifeval
  • ifbench
  • rlvr
  • lfm2
  • lfm2.5
  • prompts
    size_categories:
  • 10K<n<100K
    source_datasets:
  • allenai/IF_multi_constraints_upto5
    configs:
  • config_name: default
    data_files:
    • split: train
      path: data/train-*.parquet

IF_multi_constraints_upto5 → LFM2.5 prompt format (for RLVR / rejection sampling / DPO)

A derivative of allenai/IF_multi_constraints_upto5 (odc-by)
normalized for fine-tuning Liquid AI LFM2 / LFM2.5 models, whose native tool-call format is Pythonic:

<|im_start|>assistant
<|tool_call_start|>[get_weather(location='Paris, France', unit='celsius')]<|tool_call_end|><|im_end|>

Prompt-only rows (prompt_only = true): Tulu-SFT instructions with up to 5 verifiable constraints from IFEval (25) and IFBench-Train (29 — disjoint from IFBench test). Each row ends in the LFM2.5 generation prompt; extra carries the verifier spec (ground_truth, constraint_type, constraint) for open_instruct/IFEvalG. This is the IF-RLVR data from Generalizing Verifiable Instruction Following (arXiv 2507.02833).

Every row was rendered through the official LiquidAI/LFM2.5-VL-3B chat template (identical to the LFM2.5
text models' template for text-only input); prompt-only rows carry no tool calls, so no round-trip check applies.

What changed vs. the source

Transform Why
Rendered with add_generation_prompt=True; no assistant turn Prompt set for on-policy sampling.
Tool names sanitized to Python identifiers (web-search → web_search), consistently in tools and calls; originals kept in renamed_tools Pythonic call syntax requires identifiers.
Exact-duplicate tool entries deduplicated Template hygiene.
Dropped: calls to undeclared tools, unparseable arguments, argument names that are not identifiers or are Python keywords (from, class), rows over 8192 tokens, rows with no assistant tokens Training hygiene.

Nothing was rephrased, re-generated, or re-labelled.

Columns

Column Type Description
id, source, split, license str provenance
messages str (JSON) canonical OpenAI-style messages; tool_calls arguments are dicts. Feed this + tools to apply_chat_template to re-render with any LFM template version.
tools str (JSON) OpenAI-style tool schemas
text str fully rendered LFM2.5 conversation, BOS included
prompt_only bool true when the row is a prompt ending in the generation prompt (no assistant tokens)
n_turns, n_tool_calls, n_tools, n_tokens, n_assistant_tokens int sizes (LFM2.5 tokenizer)
renamed_tools str (JSON) {original: sanitized} when any tool was renamed, else ""
extra str (JSON) source-specific fields: key, ground_truth (verifier args), dataset, constraint_type, constraint

Stats

Split Read Kept Rows with renamed tools Dropped (reason=count)
train 95,373 95,264 0 too_long=109

Training notes

  • Use assistant-only loss: apply_chat_template(messages, tools=tools, tokenize=True, return_assistant_tokens_mask=True).
  • Prefer re-rendering from messages/tools over training on text if your template differs.
  • Serving-side parsers must accept JSON literals (true, null, nested {}/[]) inside Pythonic calls.

Citation

Please cite the upstream dataset: https://huggingface.co/datasets/allenai/IF_multi_constraints_upto5

README history 2 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-20Add files using upload-large-folder toolfd012233.6 KB
    Loading...
  2. 2026-08-20initial commit7d81aa60 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("hungbenjamin402/IF-multi-constraints-upto5-LFM2.5-prompts")
Raw snapshot (Python)
from huggingface_hub import snapshot_download
snapshot_download(repo_id="hungbenjamin402/IF-multi-constraints-upto5-LFM2.5-prompts", repo_type="dataset")
git clone (requires git-lfs)
git clone https://huggingface.co/datasets/hungbenjamin402/IF-multi-constraints-upto5-LFM2.5-prompts
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