Triple
T35909819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leipzig-Engelsdorf subcamp |
E1038574
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | satellite camp of Buchenwald concentration camp |
C40337
|
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: satellite camp of Buchenwald concentration camp Context triple: [Leipzig-Engelsdorf subcamp, instanceOf, satellite camp of Buchenwald concentration camp]
-
A.
Flossenbürg subcamp
A Flossenbürg subcamp was a satellite concentration camp administratively controlled by the main Flossenbürg camp, where prisoners were exploited for forced labor under brutal conditions.
-
B.
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.
-
C.
World War II incarceration camp
chosen
A World War II incarceration camp is a government-run facility where civilians or prisoners of war were forcibly confined, often without due process, under harsh and restrictive conditions during the Second World War.
-
D.
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.
-
E.
concentration camp staff
Individuals employed by or serving in a concentration camp who are responsible for its administration, operation, security, and enforcement of policies, often participating in or facilitating systematic abuse and atrocities against detainees.
- 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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.