evaluate 0 0 0

EliasHossain/ptc-benchmark

published by @EliasHossain

Alignment dataset tracked in the /datasets sub-catalog.

Lifetime downloads
182
Last 30 days
43
Likes
-
Size
8.3 MB
Created on HF
2026-05-24
Age
5 months ago

Description

PTC Benchmark: Parametric Temporal Conflict

A verified benchmark for studying Parametric Temporal Conflict (PTC), a

failure mode in which open-weight language models default to outdated

answers under standard prompting even though the newer answer is

recoverable from parametric memory under a temporal cue.

Splits

Split

Records

Use

train

8,746

Full benchmark; headline numbers in the paper.

subset

500

Fast reviewer/reproduction split (~10 min on one… See the full description on the dataset page: https://huggingface.co/datasets/EliasHossain/ptc-benchmark.

Tags

task_categories:question-answeringlanguage:enlicense:mitsize_categories:1K<n<10Kformat:jsonmodality:tabularmodality:textlibrary:datasetslibrary:pandaslibrary:polarslibrary:mlcroissantregion:ustemporal-reasoningknowledge-conflictsfactualityparametric-memoryactivation-steering

README current version from Hugging Face


license: mit
task_categories:

  • question-answering
    language:
  • en
    size_categories:
  • 1K<n<10K
    pretty_name: Parametric Temporal Conflict (PTC) Benchmark
    version: 1.0.0
    date_published: 2026-05-24
    tags:
  • temporal-reasoning
  • knowledge-conflicts
  • factuality
  • parametric-memory
  • activation-steering
    configs:
  • config_name: default
    data_files:
    • split: train
      path: data/train.jsonl
    • split: subset
      path: data/subset.jsonl

citation: |
@misc{ptc_benchmark_2026,
title = {PTC Benchmark: Parametric Temporal Conflict},
author = {Saha, Sourav and Hossain, Elias},
year = {2026},
url = {https://huggingface.co/datasets/EliasHossain/ptc-benchmark}
}

PTC Benchmark: Parametric Temporal Conflict

A verified benchmark for studying Parametric Temporal Conflict (PTC), a
failure mode in which open-weight language models default to outdated
answers under standard prompting even though the newer answer is
recoverable from parametric memory under a temporal cue.

Splits

Split Records Use
train 8,746 Full benchmark; headline numbers in the paper.
subset 500 Fast reviewer/reproduction split (~10 min on one GPU).

Schema

One JSONL record per line. Each record is a verified temporal-fact
quadruple (q, a_old, a_new, t_update) mined from Wikidata.

Field Type Meaning
subject_qid, subject_label str Wikidata entity (e.g., Q1296, "Ghent")
relation_pid, relation_label str Wikidata property (P6, P35, P169, P286, P488)
domain str politics, corporate_leadership, sports
a_old_qid, a_old_label str The outdated answer (prior holder of the role)
a_new_qid, a_new_label str The current answer (new holder after the update)
t_old_start, t_old_end str Validity window of a_old (ISO date)
t_new_start, t_new_end str Validity window of a_new (ISO date)
t_update str Date of the superseding update
prompt_standard str Open-ended question, no temporal cue
prompt_temporal str Same question with "As of " temporal cue
coverage_tier str Verification tier from Wikidata
passed_filter bool Whether the record passes the construction filter

Relations covered

  • P35 — head of state
  • P6 — head of government
  • P169 — chief executive officer
  • P286 — head coach
  • P488 — chairperson

The distribution is intentionally unbalanced and reflects the size of each
position-holder population at source (P6 / P286 / P488 are the largest;
P35 / P169 are the smallest).

Loading

from datasets import load_dataset

# Full benchmark
ds = load_dataset("EliasHossain/ptc-benchmark", split="train")
print(ds[0])

# Fast reviewer subset
ds_small = load_dataset("EliasHossain/ptc-benchmark", split="subset")

Or stream individual records:

import json
with open("data/train.jsonl") as f:
    for line in f:
        rec = json.loads(line)
        print(rec["prompt_standard"], "->", rec["a_old_label"], "/", rec["a_new_label"])

Construction

Records are mined from Wikidata's time-bounded statements about role
holders (e.g., head of state of a country, CEO of a company). Each record
is admitted only if all of the following hold:

  1. The update is superseding rather than additive (e.g., a new CEO
    replaces the previous one, not adds to a list).
  2. The a_old and a_new validity windows are non-overlapping.
  3. Both answers are grammatically and factually plausible completions of
    the prompt.

A model-side knowledge-recovery filter is applied separately per
evaluator model at inference time: the record is in the verified PTC
subset for that model iff
mean_logprob(a_new | prompt_temporal) >= -3.0.

Source

Wikidata public statements (CC0). All entity labels and validity windows
are derived from public Wikidata dumps.

License

MIT.

Citation

@misc{ptc_benchmark_2026,
  title  = {PTC Benchmark: Parametric Temporal Conflict},
  author = {Saha, Sourav and Hossain, Elias},
  year   = {2026},
  url    = {https://huggingface.co/datasets/EliasHossain/ptc-benchmark}
}

The accompanying code is at
https://github.com/eliashossain001/temporal-attractor-steering
(or its anonymous mirror).

Contributors

  • Sourav Saha, University of Central Florida
  • Elias Hossain, University of Central Florida

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-24Add citation, version, date_published for Croissant validationdb9cb145 KB
    Loading...
  2. 2026-05-24Initial release: PTC benchmark (train=8746, subset=500)b26530b4.6 KB
    Loading...
  3. 2026-05-24initial commitd5b29720 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-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("EliasHossain/ptc-benchmark")
Raw snapshot (Python)
from huggingface_hub import snapshot_download
snapshot_download(repo_id="EliasHossain/ptc-benchmark", repo_type="dataset")
git clone (requires git-lfs)
git clone https://huggingface.co/datasets/EliasHossain/ptc-benchmark
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