Triple
T35310076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Höfle Telegram |
E1019745
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Holocaust evidence |
C40923
|
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 evidence Context triple: [Höfle Telegram, instanceOf, Holocaust evidence]
-
A.
Holocaust document
chosen
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.
-
B.
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.
-
C.
Holocaust representation
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-era artifact
A Holocaust-era artifact is a physical object originating from or directly connected to the events, people, or institutions of the Holocaust, serving as tangible evidence of persecution, survival, and memory.
-
E.
Holocaust commemoration
Holocaust commemoration is the collective practice of remembering and honoring the victims and survivors of the Holocaust through ceremonies, education, memorials, and cultural expressions to preserve historical truth and prevent future atrocities.
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.