Triple
T33544511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danica concentration camp |
E859166
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ustaše-run 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: Ustaše-run concentration camp Context triple: [Danica concentration camp, instanceOf, Ustaše-run 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.
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.
-
E.
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.
- 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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:39 a.m.