Triple
T7940938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikhail Bestuzhev-Ryumin |
E184387
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian army officer |
C449
|
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 army officer Context triple: [Mikhail Bestuzhev-Ryumin, instanceOf, Russian army officer]
-
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.
Yugoslav military officer
A Yugoslav military officer is a commissioned member of the armed forces of the former Socialist Federal Republic of Yugoslavia, responsible for leading troops, planning and executing military operations, and upholding the doctrines and political-military objectives of the Yugoslav state.
-
C.
military officer
chosen
A military officer is a formally commissioned leader in the armed forces responsible for planning, directing, and managing operations, personnel, and resources to achieve strategic and tactical objectives.
-
D.
Russian prince
A Russian prince is a male noble of princely rank in Russia, historically belonging to the aristocratic ruling class and often holding political, military, or territorial authority within the Russian Empire or its predecessor states.
-
E.
Serbian general
A Serbian general is a high-ranking military officer from Serbia responsible for leading and commanding large military formations, planning operations, and shaping national defense strategy.
- 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_69ca8291c2008190b1b8832c87814bcf |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 5:08 p.m.