Triple
T15054769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elisiv of Kiev |
E379460
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Kievan Rusʼ noble |
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ʼ noble Context triple: [Elisiv of Kiev, instanceOf, Kievan Rusʼ noble]
-
A.
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.
-
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.
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.
-
D.
Grand Prince of Kiev
The Grand Prince of Kiev was the supreme ruler of Kievan Rus', serving as the principal political, military, and often spiritual leader who held primacy over other regional princes in the federation of East Slavic territories.
-
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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3:01 a.m.