evaluate 0 0 0

memo-ozdincer/jepadata

published by @memo-ozdincer

Alignment dataset tracked in the /datasets sub-catalog.

Lifetime downloads
756
Last 30 days
42
Likes
1
Size
1.7 GB
Created on HF
2026-05-02
Age
5 months ago

Description

JepaData: 269K Adversarial Trajectories for LLM Safety

269,453 verified adversarial prompt–response trajectories for training and

evaluating jailbreak-resistant language models. JepaData spans eight attack

families and includes both harmful behaviors and benign prompts selected to

measure over-refusal.

The dataset was built as part of the large-scale adversarial data pipeline for

JEPA-Align and includes per-example attack, model, source, and transferability

provenance.… See the full description on the dataset page: https://huggingface.co/datasets/memo-ozdincer/jepadata.

Tags

task_categories:text-generationlanguage:enlicense:othersize_categories:100K<n<1Mformat:jsonmodality:textlibrary:datasetslibrary:pandaslibrary:polarslibrary:mlcroissantregion:usjailbreaksafetyalignmentred-teamingadversarial-robustnessllm-safetytool-use

README current version from Hugging Face


license: other
language:

  • en
    tags:
  • jailbreak
  • safety
  • alignment
  • red-teaming
  • adversarial-robustness
  • llm-safety
  • tool-use
    task_categories:
  • text-generation
    pretty_name: "JepaData: 269K Adversarial Trajectories for LLM Safety"
    size_categories:
  • 100K<n<1M
    configs:
  • config_name: default
    data_files:
    • split: train
      path: pairs_chat.jsonl

JepaData: 269K Adversarial Trajectories for LLM Safety

269,453 verified adversarial prompt–response trajectories for training and
evaluating jailbreak-resistant language models. JepaData spans eight attack
families and includes both harmful behaviors and benign prompts selected to
measure over-refusal.

The dataset was built as part of the large-scale adversarial data pipeline for
JEPA-Align and includes per-example attack, model, source, and transferability
provenance.

Dataset at a glance

Metric Value
Total trajectories 269,453
Harmful-side trajectories ~225K (83%)
Benign over-refusal trajectories ~44K (17%)
Attack families 8
Largest attack families Encoding, prefilling, persona

Attack distribution

Attack Trajectories Generation method
Encoding 125,129 Deterministic transformations including ROT13 and Base64
Prefilling 92,531 Assistant-response prefilling
Persona 35,462 Attacker-model rewrites
Inpainting 5,226 Attacker-model rewrites
Multi-turn 4,239 Attacker-model conversations
Direct 3,391 Unmodified target prompts
Distraction 2,350 Benign distractor injection
Best-of-N 1,125 Sampled adversarial variants

How it was generated

For each source behavior, the pipeline:

  1. generates an adversarial view using a deterministic transformation or an
    attacker language model;
  2. sends that view to a target model and records the complete rollout;
  3. evaluates whether the attack transfers with a stock Qwen3-32B verifier; and
  4. retains trajectories meeting the transferability threshold.

The attacker model for model-generated transformations is
huihui-ai/Qwen3-32B-abliterated. Target rollouts come from that model and
Qwen/Qwen3-32B; the exact source is recorded per example in
metadata.generated_with_model and metadata.transfer_target.

Source behaviors

Source Role Approximate size
Circuit Breakers training set Harmful behaviors ~225K trajectories
OR-Bench training set Benign, refusal-prone prompts ~44K trajectories

HarmBench is excluded from training and reserved for evaluation.

Load the dataset

from datasets import load_dataset

dataset = load_dataset("memo-ozdincer/jepadata", split="train")
print(dataset[0])

Each row contains chat-formatted messages plus provenance fields describing
the source behavior, attack family, generating model, target model, and
transferability score. See DATA_SCHEMA.md for the complete
field reference.

Files

File Contents
pairs_chat.jsonl Primary 269K-record dataset in chat format
metadata.json Counts by attack, side, split, and source
audit_report.json Dataset-schema and integrity audit
generators.json Attack-generator descriptions
DATA_SCHEMA.md Field-level schema reference

Intended use

  • Training defenses against adversarially reframed harmful requests
  • Training and evaluating jailbreak-detection models
  • Studying attack transfer across model and prompt families
  • Measuring safety–utility and over-refusal tradeoffs
  • Constructing held-out red-team evaluations

This dataset contains successful jailbreaks and harmful model outputs. It is
intended for defensive safety research and should not be used to enable attacks
against deployed systems.

Data quality and provenance

  • Every retained record passes the dataset's transferability gate.
  • Early trajectories use the abliterated Qwen3-32B model as both generator and
    target; later trajectories use stock Qwen3-32B as the target. Use the
    per-record provenance fields when selecting a specific target distribution.
  • 435 benign rows overlap with OR-Bench-Test. Exclude them before evaluating on
    that benchmark to prevent train–test overlap.
  • Attack families are intentionally imbalanced because successful transfer
    rates differ substantially across attacks.

Example OR-Bench filtering:

from datasets import load_dataset

test_prompts = set(
    load_dataset("bench-llm/or-bench", "or-bench-test", split="train")["prompt"]
)
dataset = load_dataset("memo-ozdincer/jepadata", split="train")
dataset = dataset.filter(lambda row: row["behavior_text"] not in test_prompts)

Related artifacts

Citation

@misc{ozdincer2026jepadata,
  title        = {JepaData: 269K Adversarial Trajectories for LLM Safety},
  author       = {Ozdincer, Memo},
  year         = {2026},
  howpublished = {Hugging Face Dataset},
  url          = {https://huggingface.co/datasets/memo-ozdincer/jepadata}
}

README history 4 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-13Polish public dataset card771d4cc5.2 KB
    Loading...
  2. 2026-05-04v1: 269,453 records, multi-cluster harvest + Phase E orbench-80Kf4406947.3 KB
    Loading...
  3. 2026-05-02Upload folder using huggingface_hub9c4370b5.4 KB
    Loading...
  4. 2026-05-02initial commit51262540 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-03[bot] Conversion to Parquetopen1 💬#1
    Loading...

Related datasets same stage · evaluate

Read further

Metadata

License
other

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