Triple
T16341015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicholas II of Russia |
E396803
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | last Emperor of Russia |
C4092
|
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: last Emperor of Russia Context triple: [Nicholas II of Russia, instanceOf, last Emperor of Russia]
-
A.
tsar of Russia
chosen
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.
Grand Duke of Russia
A Grand Duke of Russia was a male member of the Russian imperial family, typically a son or grandson of a reigning emperor, who held high dynastic rank and status without necessarily exercising sovereign rule.
-
C.
Empress of Russia
The Empress of Russia is the female sovereign ruler or consort at the apex of the Russian imperial hierarchy, embodying supreme political authority, dynastic continuity, and ceremonial leadership within the Russian Empire.
-
D.
Grand Duchess of Russia
A Grand Duchess of Russia is a female member of the Russian imperial family, typically the daughter or granddaughter of a reigning emperor (tsar) or sometimes the wife of a grand duke, holding high dynastic rank and social status within the empire.
-
E.
Grand Prince of Moscow
The Grand Prince of Moscow was the medieval ruler of the Grand Duchy of Moscow, who gradually consolidated Russian lands, led resistance against foreign domination, and laid the foundations for a centralized Russian state.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:07 a.m.