Triple
T25361300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Friedrich Wilhelm von Buxhoeveden |
E635973
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian Imperial general |
C37608
|
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: Russian Imperial general Context triple: [Friedrich Wilhelm von Buxhoeveden, instanceOf, Russian Imperial general]
-
A.
Imperial Russian Army general
chosen
An Imperial Russian Army general is a high-ranking military officer of the Russian Empire responsible for commanding large formations, planning and directing operations, and implementing imperial military policy.
-
B.
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.
-
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.
Russian admiral
A Russian admiral is a high-ranking naval officer in the Russian Navy responsible for commanding fleets or major naval formations and shaping maritime strategy and operations.
-
E.
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.
- 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_69e75a9b7cf481909f2dcdfb37d95ca7 |
completed | April 21, 2026, 11:08 a.m. |
Created at: April 21, 2026, 1:36 p.m.