Triple
T29835554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rurikid principalities |
E757648
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | successor states of Kievan Rus' |
C9058
|
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: successor states of Kievan Rus' Context triple: [Rurikid principalities, instanceOf, successor states of Kievan Rus']
-
A.
medieval East Slavic state
A medieval East Slavic state is a historically situated political entity formed by East Slavic peoples between the 9th and 15th centuries, characterized by princely rule, Orthodox Christianity, and a feudal socio-economic structure.
-
B.
Russian principality
chosen
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.
-
C.
Mongol successor state
A Mongol successor state is a political entity that emerged from the fragmentation of the Mongol Empire, inheriting its territories, institutions, and ruling elites while developing distinct regional identities and governance structures.
-
D.
institution of the Novgorod Republic
The institution of the Novgorod Republic was a medieval political and administrative system centered on a veche (popular assembly), elected officials, and a powerful merchant elite that collectively governed the city-state and its vast northern territories.
-
E.
Slavic state
A Slavic state is a political entity whose dominant population, culture, and often official language are rooted in one or more Slavic ethnic groups.
- 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:36 p.m.