Triple
T11164226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holocaust in Hungary |
E264119
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Holocaust event |
C2184
|
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 event Context triple: [Holocaust in Hungary, instanceOf, Holocaust event]
-
A.
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.
-
B.
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.
-
C.
event in Nazi Germany
chosen
An event in Nazi Germany is a historically situated occurrence—political, social, military, cultural, or economic—that took place under the National Socialist regime between 1933 and 1945 and contributed to its policies, ideology, or consequences.
-
D.
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.
-
E.
Holocaust-related organization
A Holocaust-related organization is an entity dedicated to documenting, commemorating, educating about, or seeking justice for the events, victims, and legacy 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:29 p.m.