Triple
T7322793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Duke Michael Nikolaevich of Russia |
E168792
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian imperial statesman |
C8762
|
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 statesman Context triple: [Grand Duke Michael Nikolaevich of Russia, instanceOf, Russian imperial statesman]
-
A.
Soviet statesman
A Soviet statesman is a high-ranking political leader or government official in the Soviet Union responsible for shaping and implementing state policy, diplomacy, and ideological direction.
-
B.
Austrian statesman
An Austrian statesman is a political leader or public official from Austria who plays a significant role in shaping the nation's domestic and foreign policies through governance, diplomacy, and legislative influence.
-
C.
tsar of Russia
The tsar of Russia was the autocratic monarch who ruled the Russian state and later empire, wielding supreme political, military, and religious authority until the monarchy’s abolition in 1917.
-
D.
Japanese statesman
A Japanese statesman is a political leader or public official who plays a significant role in shaping Japan’s governmental policies, diplomatic relations, and national development.
-
E.
Russian Empire person
chosen
A Russian Empire person is an individual who lived under the sovereignty of the Russian Empire, shaped by its political structures, social hierarchies, and cultural milieu between the early 18th and early 20th centuries.
- 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_69c68a54cacc81908e3b773441f19566 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:03 p.m.