Triple
T3822505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ziegenberg (near Bad Nauheim) in later war years |
E88605
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Wehrmacht headquarters |
C14450
|
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: Wehrmacht headquarters Context triple: [Ziegenberg (near Bad Nauheim) in later war years, instanceOf, Wehrmacht headquarters]
-
A.
Wehrmacht high command
The Wehrmacht high command was the central military leadership of Nazi Germany responsible for planning, directing, and coordinating the operations of the German armed forces during the Second World War.
-
B.
army of the Wehrmacht
The army of the Wehrmacht was Nazi Germany’s unified land warfare force from 1935 to 1945, responsible for conducting large-scale military operations and invasions across Europe and beyond during World War II.
-
C.
Wehrmacht corps
A Wehrmacht corps was a mid-level German Army formation in World War II, typically commanding several divisions and supporting units to conduct coordinated operations within a larger army structure.
-
D.
Waffen-SS corps
The Waffen-SS corps was the combat branch of Nazi Germany’s SS organization, comprising ideologically driven, militarized units that fought alongside the regular army and were heavily involved in war crimes and atrocities during World War II.
-
E.
Waffen-SS armoured corps
The Waffen-SS armoured corps was the armoured warfare branch of Nazi Germany’s Waffen-SS, comprising elite but ideologically driven tank and mechanized formations that fought alongside the regular army on multiple fronts during World War II.
- 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_69aed9538cf881909d9ce8ca4ac7c18c |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.