Triple
T15750041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holocaust education networks |
E381820
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Holocaust education infrastructure |
C35833
|
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 education infrastructure Context triple: [Holocaust education networks, instanceOf, Holocaust education infrastructure]
-
A.
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.
-
B.
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.
-
C.
Jewish educational typology
Jewish educational typology is a conceptual framework that categorizes the diverse forms, philosophies, and institutional models of Jewish learning across historical periods, denominations, and cultural contexts.
-
D.
Holocaust site
A Holocaust site is a location directly associated with the persecution, deportation, forced labor, or mass murder of Jews and other targeted groups by Nazi Germany and its collaborators during the Holocaust.
-
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. chosen
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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:47 a.m.