Triple
T31705175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESMA detention center |
E809158
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | extermination center |
C59388
|
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: extermination center Context triple: [ESMA detention center, instanceOf, extermination center]
-
A.
killing facility
A killing facility is a location specifically designed and equipped to systematically carry out the deliberate killing of living beings, often on an organized or industrial scale.
-
B.
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.
-
C.
Nazi concentration and extermination camp
A Nazi concentration and extermination camp was a state-organized facility in which the Nazi regime systematically imprisoned, exploited, tortured, and murdered millions of people—primarily Jews, along with other persecuted groups—as part of its genocidal policies during the Holocaust.
-
D.
Gestapo prison
A Gestapo prison is a detention facility operated by Nazi Germany’s secret state police, used to incarcerate, interrogate, and torture political opponents, resistance members, and other targeted groups.
-
E.
World War II ghetto
A World War II ghetto was a segregated, enclosed urban district where Nazi authorities forcibly confined Jews (and sometimes other targeted groups) under overcrowded, impoverished, and brutal conditions as part of their broader system of persecution and genocide.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:13 p.m.