Triple
T1139163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Duke Michael Alexandrovich of Russia |
E23409
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heir to the Russian throne |
C4886
|
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: heir to the Russian throne Context triple: [Grand Duke Michael Alexandrovich of Russia, instanceOf, heir to the Russian throne]
-
A.
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.
-
B.
member of the House of Romanov
chosen
A member of the House of Romanov is an individual belonging by birth or marriage to the former imperial dynasty that ruled Russia from 1613 until the abdication of Tsar Nicholas II in 1917.
-
C.
claimant to the English throne
A claimant to the English throne is an individual who asserts a legitimate right, by bloodline, marriage, conquest, or political claim, to be recognized as the lawful monarch of England.
-
D.
Russian grand duchess
A Russian grand duchess is a female member of the Russian imperial family, typically the daughter or granddaughter of a tsar, holding high noble rank and associated with significant social and political status in the Russian Empire.
-
E.
heir presumptive to the British throne
A heir presumptive to the British throne is the person currently first in line to inherit the crown whose claim can be displaced by the birth of a more eligible heir, such as a legitimate child of the reigning monarch.
- 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_69a493ef399c8190b04b9146d2314f59 |
completed | March 1, 2026, 7:30 p.m. |
Created at: March 1, 2026, 7:44 p.m.