Triple
T14973452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rogneda of Polotsk |
E373383
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | person of Kievan Rus' |
C12793
|
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: person of Kievan Rus' Context triple: [Rogneda of Polotsk, instanceOf, person of Kievan Rus']
-
A.
ruler of Kievan Rus'
A ruler of Kievan Rus' is the supreme political and military leader of the medieval East Slavic state centered in Kyiv, responsible for governing its territories, directing foreign policy, and upholding dynastic authority.
-
B.
monarch of Kievan Rus'
A monarch of Kievan Rus' is the supreme hereditary ruler—typically titled grand prince—who governed the medieval East Slavic polity centered on Kyiv, overseeing its military, legal, religious, and diplomatic affairs.
-
C.
Rurikid prince
A Rurikid prince is a medieval ruler or dynastic member descended from the Varangian leader Rurik, who governed principalities across Kievan Rus' and its successor states.
-
D.
princess of Kievan Rus'
A princess of Kievan Rus' is a high-born woman of the ruling Rurikid dynasty who played key roles in dynastic alliances, governance, and the cultural and religious life of the medieval East Slavic state.
-
E.
member of the Rurik dynasty
chosen
A member of the Rurik dynasty is an individual belonging to the medieval ruling family traditionally traced to the Varangian prince Rurik, which governed parts of Eastern Europe, including Kievan Rus and later principalities, from the 9th to the 16th 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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:50 a.m.