Triple
T32584193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur Butz |
E832873
|
entity |
| Predicate | hasBeenCondemnedFor |
P42784
|
FINISHED |
| Object | Holocaust denial statements |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Holocaust denial statements | Statement: [Arthur Butz, hasBeenCondemnedFor, Holocaust denial statements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenCondemnedFor Context triple: [Arthur Butz, hasBeenCondemnedFor, Holocaust denial statements]
-
A.
condemnedBy
Indicates that an entity is judged, denounced, or declared wrong or unacceptable by another entity.
-
B.
condemnedAs
Indicates that one entity formally or strongly denounces another entity by labeling it as wrong, guilty, or unacceptable.
-
C.
condemnedIn
Indicates that an entity was formally denounced, sentenced, or declared guilty within a particular place, context, or proceeding.
-
D.
subjectOfCondemnation
chosen
Indicates that one entity is the target or object of formal disapproval, criticism, or denunciation by another entity.
-
E.
condemnedTo
Indicates that one entity has been sentenced or assigned by another entity to undergo a specific punishment, usually involving severe or irreversible consequences.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 1, 2026, 1:04 a.m.