Triple
T916735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander II of Russia |
E19788
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian emperor |
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: Russian emperor Context triple: [Alexander II of Russia, instanceOf, Russian emperor]
-
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.
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.
-
C.
Emperor of India
The "Emperor of India" was a sovereign title used by the British monarch from 1876 to 1948 to signify their supreme imperial authority over the territories of the Indian subcontinent under British rule.
-
D.
King of France
The King of France is the sovereign monarch who historically ruled the Kingdom of France, embodying supreme political authority, symbolic national leadership, and dynastic continuity until the abolition of the monarchy.
-
E.
Empress consort of Russia
The Empress consort of Russia was the wife of the reigning Russian emperor (tsar), holding a high ceremonial and social status at court, often influencing politics, culture, and dynastic affairs without ruling in her own right.
- 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_69a4939f91a08190ba68c2c81eab90fe |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:39 p.m.