Triple
T10326471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karl-Wilhelm von Schlieben |
E242775
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German Army general |
C27859
|
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: German Army general Context triple: [Karl-Wilhelm von Schlieben, instanceOf, German Army general]
-
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.
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.
-
C.
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.
-
D.
Belgian general
A Belgian general is a high-ranking military officer from Belgium responsible for leading large military formations, developing strategic plans, and overseeing operations within the Belgian Armed Forces or in multinational contexts.
-
E.
Czech general
A Czech general is a high-ranking military officer from the Czech Republic responsible for leading armed forces, formulating defense strategies, and overseeing military operations and personnel.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:51 a.m.