Triple
T15041987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eupraxia of Kiev |
E378621
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Kievan Rus' nobility |
C12606
|
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: Kievan Rus' nobility Context triple: [Eupraxia of Kiev, instanceOf, Kievan Rus' nobility]
-
A.
Bulgarian nobles
Bulgarian nobles are members of the historical aristocratic class in Bulgaria who held hereditary titles, land, and political influence, shaping the country’s medieval and early modern governance, culture, and military affairs.
-
B.
Finnish noble
A Finnish noble is a member of the historical aristocratic class in Finland, traditionally holding hereditary titles, land, and social privileges recognized by the Swedish and later Russian crowns, and organized through institutions such as the Finnish House of Nobility.
-
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.
Rurikid prince
chosen
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.
-
E.
Bulgarian noble
A Bulgarian noble is a member of the historical aristocratic class in Bulgaria, holding hereditary titles, land, and political influence within the medieval or early modern Bulgarian 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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3 a.m.