evaluate 0 0 0

jensjepsen/danish-if-grpo-combined-v3

published by @jensjepsen

Alignment dataset tracked in the /datasets sub-catalog.

Lifetime downloads
72
Last 30 days
17
Likes
-
Size
15.8 MB
Created on HF
2026-08-24
Age
1 months ago

Description

danish-if-grpo-combined-v3

10,000 Danish instruction-following prompts for GRPO reward training,

built by rewriting danish-instruction-following-v4 prompts with a

sampled mix of our 46 Danish constraints + ~24 Google IFEval-schema

constraints.

What's new vs v2

Structural fixes (see scripts/constraint_compat.py on

github):

0% impossible constraint combos (v2 had 15.2%; e.g. constrained_response

paired with 20+ content-shape rules that can't co-satisfy). Enforced… See the full description on the dataset page: https://huggingface.co/datasets/jensjepsen/danish-if-grpo-combined-v3.

Tags

task_categories:text-generationlanguage:dalicense:mitsize_categories:10K<n<100Kformat:arrowmodality:tabularmodality:textlibrary:datasetslibrary:mlcroissantregion:usdanishgrpoinstruction-followingif-eval

README current version from Hugging Face


license: mit
language: da
tags:

  • danish
  • grpo
  • instruction-following
  • if-eval
    task_categories:
  • text-generation
    size_categories:
  • 1K<n<100K

danish-if-grpo-combined-v3

10,000 Danish instruction-following prompts for GRPO reward training,
built by rewriting danish-instruction-following-v4 prompts with a
sampled mix of our 46 Danish constraints + ~24 Google IFEval-schema
constraints.

What's new vs v2

Structural fixes (see scripts/constraint_compat.py on
github):

  • 0% impossible constraint combos (v2 had 15.2%; e.g. constrained_response
    paired with 20+ content-shape rules that can't co-satisfy). Enforced via a
    reject-sampling loop with an explicit alias-map + pair-incompatibility table.
  • Namespace deduped — no more rows with both google:startend:quotation
    and its custom alias entire_in_quotes (v2 had 260+).

Language / quality fixes (Gemini template + verify-retry):

  • English contamination on case rules 95% → 0.1% — english_capital /
    english_lowercase descriptions swapped to Danish (verifier is already
    Danish-aware; only the source text was steering the model to English).
  • English constraint verbatim 11.3% → 4.5% — explicit "OVERSÆT engelske
    regler til dansk" instruction to the rewriter.
  • Missing task text 9.3% → 6.5% — explicit "GRUNDOPGAVEN skal fremgå
    TYDELIGT" requirement.
  • Constraint dropped from prompt 17.6% → 12.8% — verify-retry loop:
    after Gemini returns, keyword-scan the new prompt against each constraint;
    if any missing, retry once with "you forgot X" hint.

Recipe

  • Source: jensjepsen/danish-instruction-following-v4 (extract raw task,
    discard old rules)
  • Constraint pool: our-46 Danish + ~24 Google IFEval; 50/50 mix, n_rules
    sampled 1-5 uniform
  • Rewriter: google/gemini-2.5-flash-lite via OpenRouter (verified
    6.25× cheaper on output than 3.5-flash-lite and also better at not
    dropping constraints)
  • Style variation: 8 orthogonal axes (placement, form, opener,
    terminator, case, quirk, tone, rephrase) cartesian-sampled per row —
    same as v2

Schema

task           : str  — the base task (post-extraction)
prompt         : str  — the new full Danish prompt (task + rules woven)
constraints    : list[str]  — canonical constraint names
params         : list[dict] — per-constraint kwargs
n_rules        : int
style_tags     : str (JSON) — 8-axis style tags used to steer the rewrite
source         : str — v4 task type (e.g. wiki:brainstorming, sciq)
old_constraints: list[str] — the rules from the source v4 row (discarded, kept for provenance)
row_idx        : int

Constraint distribution (top 15)

Same shape as v2. Top offenders that used to break v2 (constrained_response,
json_format paired with wrappers, two_responses × quotation) are now
rejected at sample time.

Known residuals

  • ~12.8% of rows still have Gemini paraphrasing a constraint too subtly for
    strict keyword matching. Manual sampling suggests most are true paraphrases
    ("nævne" instead of "inkludér", "skal indgå" instead of "brug ordet") —
    not real drops. Real drop rate probably closer to 5-8%.
  • 4.5% still contain English constraint text verbatim (some Google
    descriptions Gemini won't Danish-ify even under prompting).

Related

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-24v3 initial upload: 0% impossible + sharpened Gemini template + verify-retrya87cc5c3.7 KB
    Loading...
  2. 2026-08-24initial commitb08df510 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-08-25[bot] Conversion to Parquetopen1 💬#1
    Loading...

Related datasets same stage · evaluate

Read further

Metadata

License
mit

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("jensjepsen/danish-if-grpo-combined-v3")
Raw snapshot (Python)
from huggingface_hub import snapshot_download
snapshot_download(repo_id="jensjepsen/danish-if-grpo-combined-v3", repo_type="dataset")
git clone (requires git-lfs)
git clone https://huggingface.co/datasets/jensjepsen/danish-if-grpo-combined-v3
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