Triple
T21859594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Generalplan Ost |
E539725
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nazi population policy plan |
C45423
|
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: Nazi population policy plan Context triple: [Generalplan Ost, instanceOf, Nazi population policy plan]
-
A.
Nazi report
A Nazi report is an official document produced by Nazi authorities or affiliated organizations that records observations, decisions, policies, or activities in line with the regime’s ideological, political, or military objectives.
-
B.
Nazi architecture project
A Nazi architecture project is a large-scale building or urban planning initiative designed under the Third Reich to embody and propagate Nazi ideology through monumental, authoritarian, and neoclassical forms.
-
C.
Nazi economic authority
A Nazi economic authority is a state-controlled institution or official body within Nazi Germany responsible for directing, regulating, and coordinating economic activity in line with the regime’s ideological, militaristic, and autarkic goals.
-
D.
Nazi Germany expansion
Nazi Germany expansion refers to the aggressive territorial and political enlargement of Germany under Adolf Hitler from 1938 to 1941 through annexations, invasions, and occupations that precipitated and escalated World War II in Europe.
-
E.
Nazi death marches
Nazi death marches were forced evacuations of concentration camp prisoners on brutal, often lethal marches near the end of World War II, intended to prevent their liberation and conceal evidence of Nazi atrocities.
- 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_69e0c47829648190bbe2d1d7033768ec |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 6:56 p.m.