Triple
T37943389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minsk ghetto killing sites |
E946544
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Holocaust killing site |
C701
|
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 killing site Context triple: [Minsk ghetto killing sites, instanceOf, Holocaust killing site]
-
A.
Holocaust site
chosen
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.
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.
-
C.
extermination center
An extermination center is a facility designed and operated for the systematic mass killing of targeted groups, often under state authority and typically associated with genocide or crimes against humanity.
-
D.
Nazi German mass murder operation
A Nazi German mass murder operation is a systematically planned and executed campaign by the Nazi regime to exterminate or annihilate targeted groups through organized killings, often using industrialized methods and state resources.
-
E.
Auschwitz concentration camp victim
A person imprisoned, persecuted, and often murdered by the Nazi regime in the Auschwitz concentration camp complex during 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.