ablate 0 0 0

jhk0317/qwen3.8-27b-refusal-ablation-artifacts

published by @jhk0317

Alignment dataset tracked in the /datasets sub-catalog.

Lifetime downloads
210
Last 30 days
210
Likes
-
Size
31.5 MB
Created on HF
2026-09-27
Age
24 days ago

Description

Qwen3.8-27B refusal-ablation — 2026-09-26 judged re-run: research artifacts

Everything except the weights from the 2026-09-26 re-run of a Qwen3.8-27B refusal-direction

ablation study: the layer-46 direction re-extraction, the LLM-judge-scored (+ human-adjudicated)

layer/alpha selection at 2048-token generation length, the full α ladder (0 / 0.25 / 0.5 / 0.75 /

1.0) evaluated on a held-out 50+50 prompt set, an agentic scenario ladder (A/B/C × permit/no-permit,

English + Korean)… See the full description on the dataset page: https://huggingface.co/datasets/jhk0317/qwen3.8-27b-refusal-ablation-artifacts.

Tags

task_categories:text-generationlanguage:enlicense:apache-2.0region:usinterpretabilityai-safetyrefusal-directionabliterationagentic-safetyresearch

README current version from Hugging Face


license: apache-2.0
task_categories:

  • text-generation
    language:
  • en
    tags:
  • interpretability
  • ai-safety
  • refusal-direction
  • abliteration
  • agentic-safety
  • research
    pretty_name: Qwen3.8-27B refusal-ablation — 2026-09-26 judged re-run artifacts

Qwen3.8-27B refusal-ablation — 2026-09-26 judged re-run: research artifacts

Everything except the weights from the 2026-09-26 re-run of a Qwen3.8-27B refusal-direction
ablation study: the layer-46 direction re-extraction, the LLM-judge-scored (+ human-adjudicated)
layer/alpha selection at 2048-token generation length, the full α ladder (0 / 0.25 / 0.5 / 0.75 /
1.0) evaluated on a held-out 50+50 prompt set, an agentic scenario ladder (A/B/C × permit/no-permit,
English + Korean), judge caches, and the pipeline source used to produce all of it.

This re-run exists because an earlier (2026-09-16) pass selected layers/alphas using 512-token,
substring-matched refusal scoring, which overcounts bypass on generations that get cut off
mid-hedge. This run uses 2048-token generations and an LLM-judge ensemble
(gpt-5.6-terra + claude-haiku-4-5-20251001) instead, with human labels filling in judge-rejected
calls.

Weights for the four α arms (α=0 is byte-identical to stock Qwen3.8-27B and not re-hosted):

Base model: Qwen/Qwen3.8-27B (Apache-2.0).

What's in here

  • run/qwen38_ablj/ — the run's raw working directory: select.log, v_ref.select.json (layer
    selection), v_ref.select.generations.jsonl / .reasoning.jsonl (select-time generations),
    eval/ (per-alpha eval_a*.jsonl + reasoning_a*.jsonl + judge outputs), judge/ (judge
    response caches, keyed by prompt+model), human/ (queue.jsonl of judge-rejected calls sent for
    human labeling, labels.jsonl of the resulting labels), ckpt/*/abliteration.json (per-alpha edit
    metadata: direction, layer, orthogonalized modules — infra hostnames redacted to <GPU_HOST>),
    ckpt/SHA256SUMS, plus pipeline logs (pipeline.log, apply.log, extract.log, probe.log).
  • run/qwen38_ablj_records.json — the model registry entries for the qwen38-27b-ablj-l46-a* arms
    (weight hashes, environment, serving config).
  • run/qwen38_ablj_select_judge.json — the judge-scored layer selection summary that picked L46.
  • run/qwen38_ablj_ladder_tables.md — rendered result tables for the full scenario ladder.
  • run/qwen_ablj_ladder.log — the ladder run's full log.
  • scenario_csv/{csv,scenario_b,scenario_c/default}[/en]/qwen38-27b-ablj-l46-a*.csv (+
    .reasoning.jsonl) — per-scenario (A/B/C), per-language (Korean default, English in en/),
    per-alpha agentic harness results: 10 trials per condition, traced, judge-scored.
  • code/ — the pipeline source (extraction, application, selection, eval, harness, judging, S3/HF
    registration). AWS account ID, bucket name, and GPU host IPs are redacted to
    <AWS_ACCOUNT> / <MODEL_STORE_BUCKET> / <GPU_HOST>; no credentials are stored in these files —
    connect.sh mints short-lived scoped AWS credentials at runtime rather than embedding any.

This is the artifact set for the 2026-09-26 run only. It does not include the original 2026-09-16
run's data (that was a separate release).

License

Apache-2.0, inherited from the base model. See LICENSE.

Citation / context

Part of an ongoing interpretability study into how a single linear direction mediates refusal
behavior in Qwen3.8-27B, and how robust that behavior is to ablating it at different scales.

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-09-27Qwen3.8-27B refusal-ablation artifacts (2026-09-26 judged re-run)cf371783.9 KB
    Loading...
  2. 2026-09-27initial commitba9320d0 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 · ablate

Read further

Metadata

License
apache-2.0

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("jhk0317/qwen3.8-27b-refusal-ablation-artifacts")
Raw snapshot (Python)
from huggingface_hub import snapshot_download
snapshot_download(repo_id="jhk0317/qwen3.8-27b-refusal-ablation-artifacts", repo_type="dataset")
git clone (requires git-lfs)
git clone https://huggingface.co/datasets/jhk0317/qwen3.8-27b-refusal-ablation-artifacts
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