Triple
T21658125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jakob Heinrich von Flemming |
E534520
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Saxon field marshal |
C45132
|
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: Saxon field marshal Context triple: [Jakob Heinrich von Flemming, instanceOf, Saxon field marshal]
-
A.
Russian field marshal
A Russian field marshal is the highest-ranking military officer in the Russian (historically Imperial or Soviet-equivalent) army, responsible for commanding large-scale operations and shaping overall military strategy.
-
B.
Georgian military commander
A Georgian military commander is a high-ranking officer from Georgia responsible for planning, directing, and overseeing military operations and strategy within the Georgian armed forces.
-
C.
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.
-
D.
British military leader
A British military leader is a high-ranking officer from the United Kingdom responsible for planning, directing, and overseeing military operations and strategy, often commanding troops in national defense or international conflicts.
-
E.
Chief of the Imperial General Staff
The Chief of the Imperial General Staff was the professional head of the British Army, responsible for strategic planning, operational command oversight, and advising the government on military matters within the British Empire.
- 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_69e0c467e1f48190af2650b19175abc4 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:36 p.m.