Triple
T29143922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saal an der Donau subcamp |
E738715
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Flossenbürg subcamp |
C54686
|
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: Flossenbürg subcamp Context triple: [Saal an der Donau subcamp, instanceOf, Flossenbürg subcamp]
-
A.
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.
-
B.
sub-unit of Einsatzgruppe C
A sub-unit of Einsatzgruppe C was a smaller operational detachment within this Nazi mobile killing squad, tasked with carrying out mass shootings, deportations, and other genocidal actions in designated areas of occupied Eastern Europe during World War II.
-
C.
Kapo
A Kapo is a prisoner assigned by camp authorities to supervise forced labor or carry out administrative tasks, often wielding power over fellow inmates within a concentration or labor camp system.
-
D.
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.
-
E.
Nazi SS office
A Nazi SS office was an administrative and operational unit of the Schutzstaffel responsible for planning, coordinating, and executing the regime’s ideological, security, and genocidal policies.
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 28, 2026, 11:38 a.m.