Triple
T33886623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holocaust denial |
E868650
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical negationism |
C58436
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historical negationism Context triple: [Holocaust denial, instanceOf, historical negationism]
-
A.
Holocaust denier
A Holocaust denier is a person who rejects, distorts, or minimizes the established historical facts of the Nazi genocide of six million Jews and millions of other victims during World War II, often for ideological or antisemitic reasons.
-
B.
revisionist historical narrative
A revisionist historical narrative is an account of past events that challenges established interpretations by reexamining evidence, perspectives, and assumptions to present an alternative understanding of history.
-
C.
international condemnation of Holocaust denial
International condemnation of Holocaust denial is the widespread, formal rejection and censure by governments, institutions, and global organizations of any attempts to deny, distort, or trivialize the historical reality and magnitude of the Holocaust.
-
D.
pseudohistorical ideology
chosen
A pseudohistorical ideology is a belief system that selectively distorts, fabricates, or misinterprets historical evidence to legitimize political, cultural, or social agendas while presenting itself as genuine history.
-
E.
historical axis
A historical axis is a conceptual timeline or reference line that organizes events, periods, or developments in chronological order to reveal patterns and relationships across history.
- F. None of above.
Provenance (1 batch)
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_69f34996761c8190864e42f7c9cf215b |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:48 a.m.