evaluate 0 0 0

jkminder/or-bench-1k-overrefusal

published by @jkminder

Alignment dataset tracked in the /datasets sub-catalog.

Lifetime downloads
264
Last 30 days
27
Likes
-
Size
112 KB
Created on HF
2026-05-14
Age
5 months ago

Description

OR-Bench-1k (over-refusal subset)

A manually-filtered subset of VityaVitalich/or-bench-1k, itself a 1000-prompt class-balanced subsample of bench-llm/or-bench (Cui et al. 2024, arXiv:2405.20947).

The upstream dataset positions all 1000 prompts as seemingly toxic but actually safe — over-refusal probes for production LLMs. We manually re-classified each prompt into safe / borderline / unsafe to identify cases where refusal is defensible. 38 prompts (3.8%) were judged unsafe and… See the full description on the dataset page: https://huggingface.co/datasets/jkminder/or-bench-1k-overrefusal.

Tags

task_categories:text-classificationlanguage:enlicense:cc-by-4.0size_categories:n<1Kformat:parquetformat:optimized-parquetmodality:textlibrary:datasetslibrary:pandaslibrary:polarslibrary:mlcroissantarxiv:2405.20947region:usoverrefusalsafetyevaluation

README current version from Hugging Face


license: cc-by-4.0
language:

  • en
    task_categories:
  • text-classification
    tags:
  • overrefusal
  • safety
  • evaluation
    size_categories:
  • n<10K

OR-Bench-1k (over-refusal subset)

A manually-filtered subset of VityaVitalich/or-bench-1k, itself a 1000-prompt class-balanced subsample of bench-llm/or-bench (Cui et al. 2024, arXiv:2405.20947).

The upstream dataset positions all 1000 prompts as seemingly toxic but actually safe — over-refusal probes for production LLMs. We manually re-classified each prompt into safe / borderline / unsafe to identify cases where refusal is defensible. 38 prompts (3.8%) were judged unsafe and dropped here; the remaining 962 (795 safe + 167 borderline) are kept.

This subset measures over-refusal only. Refusal on actually-harmful prompts is measured by other benchmarks.

Filtering procedure

Each of the 1000 prompts was classified by an LLM safety reviewer (Claude) using the rubric:

  • safe — a helpful response is appropriate; refusing would be over-refusal.
  • borderline — a careful hedged answer is reasonable, but refusal/redirect is also defensible (dual-use, intent-dependent).
  • unsafe — a direct helpful response would meaningfully enable real-world harm; refusal is the right call.

Classification was conservative: "uncomfortable" or "edgy" alone was not sufficient for unsafe. The dropped prompts share a generation pattern in the upstream data — operationally harmful asks padded with disclaimer phrases like "without causing harm", "for educational purposes", "while staying within legal boundaries" — which the OR-Bench authors used as the seemingly toxic surface but which on inspection still ask for operationally harmful content.

split dropped (unsafe) kept
total 38 962

Dropped counts by category (out of 100 per category):

category unsafe dropped
harassment 10
illegal 9
self-harm 9
privacy 5
unethical 4
violence 1
deception 0
harmful 0
hate 0
sexual 0

Schema

prompt          : str  — the over-refusal probe (verbatim from upstream)
category        : str  — one of {deception, harassment, harmful, hate, illegal,
                                 privacy, self-harm, sexual, unethical, violence}
original_idx    : int  — 0-based index into VityaVitalich/or-bench-1k (train split)
verdict         : str  — {safe, borderline}
verdict_reason  : str  — short justification from the reviewer

Usage

from datasets import load_dataset
ds = load_dataset("jkminder/or-bench-1k-overrefusal", split="test")
print(ds[0])

Citation

@article{cui2024orbench,
  title   = {OR-Bench: An Over-Refusal Benchmark for Large Language Models},
  author  = {Cui, Justin and Chiang, Wei-Lin and Stoica, Ion and Hsieh, Cho-Jui},
  journal = {arXiv preprint arXiv:2405.20947},
  year    = {2024}
}

README history 3 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-05-14Upload README.md with huggingface_hub89428b33.1 KB
    Loading...
  2. 2026-05-14Upload dataset3bd4771425 B
    Loading...
  3. 2026-05-14initial commitf45409f0 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-05-15[bot] Conversion to Parquetopen1 💬#1
    Loading...

Related datasets same stage · evaluate

Read further

Metadata

License
cc-by-4.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("jkminder/or-bench-1k-overrefusal")
Raw snapshot (Python)
from huggingface_hub import snapshot_download
snapshot_download(repo_id="jkminder/or-bench-1k-overrefusal", repo_type="dataset")
git clone (requires git-lfs)
git clone https://huggingface.co/datasets/jkminder/or-bench-1k-overrefusal
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