Triple
T7270237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helmuth von Moltke the Younger |
E161082
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Chief of the German General Staff |
C21013
|
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: Chief of the German General Staff Context triple: [Helmuth von Moltke the Younger, instanceOf, Chief of the German General Staff]
-
A.
Prussian general
A Prussian general is a high-ranking military officer of the historical Kingdom of Prussia, characterized by rigorous discipline, strategic planning, and leadership in organizing and commanding armies in war.
-
B.
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.
-
C.
general of the army
A general of the army is the highest-ranking military officer responsible for overseeing large-scale strategic planning, command, and coordination of an entire nation's land forces.
-
D.
Austrian general
An Austrian general is a high-ranking military officer from Austria responsible for planning, directing, and overseeing large-scale military operations and strategic defense initiatives.
-
E.
Polish military leader
A Polish military leader is a high-ranking commander from Poland responsible for planning, directing, and overseeing military operations and the strategic use of armed forces in defense of the nation.
- 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_69c6885181008190b419040e22939c7c |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:58 p.m.