Triple
T12254112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sobibor extermination camp uprising |
E292054
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Holocaust resistance event |
C13327
|
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 resistance event Context triple: [Sobibor extermination camp uprising, instanceOf, Holocaust resistance event]
-
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.
organization aiding Jews during the Holocaust
An organization aiding Jews during the Holocaust is a group that covertly or openly provided protection, resources, escape routes, and other life-saving assistance to Jewish individuals and communities persecuted by the Nazi regime and its collaborators.
-
C.
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.
-
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.
World War II resistance operation
chosen
A World War II resistance operation is a covert, organized action conducted by underground groups in occupied territories to sabotage enemy forces, gather intelligence, and support Allied war efforts.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:52 p.m.