Triple
T28087104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rethinking the Holocaust |
E709853
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Holocaust studies book |
C13941
|
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: Holocaust studies book Context triple: [Rethinking the Holocaust, instanceOf, Holocaust studies book]
-
A.
Holocaust and Gulag literature
Holocaust and Gulag literature comprises works that depict, analyze, and bear witness to the experiences, atrocities, and moral questions arising from Nazi concentration camps and Soviet forced labor camps.
-
B.
Holocaust document
A Holocaust document is any contemporaneous or retrospective record—such as letters, reports, photographs, diaries, or official forms—that provides evidence, testimony, or administrative detail about the persecution and genocide of Jews and other targeted groups by Nazi Germany and its collaborators.
-
C.
Holocaust representation
chosen
Holocaust representation is the diverse set of artistic, literary, cinematic, and memorial practices that depict, interpret, and respond to the historical events and traumatic legacy of the Holocaust.
-
D.
Holocaust historian
A Holocaust historian is a scholar who researches, analyzes, and interprets the origins, events, experiences, and aftermath of the Holocaust to document its history and preserve its memory.
-
E.
Holocaust-related collection
A Holocaust-related collection is an organized body of materials—such as documents, artifacts, testimonies, and media—that directly pertain to the events, experiences, and historical context of the Holocaust.
- 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
Created at: April 27, 2026, 8:55 p.m.