Triple
T7889496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oberbefehlshaber West |
E183190
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Wehrmacht high command authority |
C10085
|
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 high command authority Context triple: [Oberbefehlshaber West, instanceOf, Wehrmacht high command authority]
-
A.
Wehrmacht high command
chosen
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.
Wehrmacht headquarters
The Wehrmacht headquarters was the central command authority of Nazi Germany's unified armed forces, responsible for strategic planning, coordination, and direction of military operations during World War II.
-
C.
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.
-
D.
Wehrmacht position
A Wehrmacht position is a designated location or role within the German armed forces of Nazi Germany during World War II, encompassing specific duties, rank, and tactical responsibilities in military operations.
-
E.
Chief of the German General Staff
The Chief of the German General Staff was the highest-ranking professional officer responsible for planning, directing, and coordinating the operations and strategy of the German Army’s General Staff.
- 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_69ca828c474c8190a254d6499871eaff |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 5 p.m.