Triple
T3447070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sviatoslav I of Kiev |
E72702
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ruler of Kievan Rus' |
C12746
|
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: ruler of Kievan Rus' Context triple: [Sviatoslav I of Kiev, instanceOf, ruler of Kievan Rus']
-
A.
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.
-
B.
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.
-
C.
Russian principality
A Russian principality is a semi-autonomous medieval or early modern territorial state ruled by a prince within the broader political and cultural sphere of Rus', often owing allegiance to a grand prince or tsar.
-
D.
King of Poland
The King of Poland was the sovereign ruler of the Polish state, historically elected by the nobility and responsible for governing the kingdom, leading its armies, and representing it in foreign affairs.
-
E.
King of Poland
The King of Poland was the sovereign ruler of the Polish state, historically elected by the nobility and responsible for governing the kingdom, leading its military, and representing it in foreign affairs.
- F. None of above. chosen
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_69ad85b05c848190b7a28ceec2bd7b74 |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:16 p.m.