Triple

T33529987
Position Surface form Disambiguated ID Type / Status
Subject Principality of Kostroma E858749 entity
Predicate instanceOf P0 FINISHED
Object Rus' principality C8750 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: Rus' principality
Context triple: [Principality of Kostroma, instanceOf, Rus' principality]
  • A. 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.
  • B. medieval East Slavic state chosen
    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.
  • C. Piast-ruled principality
    A Piast-ruled principality is a medieval territorial polity in Central Europe governed by a member of the Piast dynasty, typically characterized by fragmented authority, hereditary rule, and integration into the broader political landscape of the Polish and neighboring realms.
  • D. Bulgarian principality
    A Bulgarian principality is a semi-autonomous, monarchical political entity historically established on Bulgarian territory, typically under the suzerainty or influence of a larger empire or state.
  • E. East Slavic polity
    An East Slavic polity is a historically or contemporarily organized political entity—such as a state, principality, or federation—primarily inhabited, shaped, or governed by East Slavic peoples (Russians, Ukrainians, Belarusians, and related 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_69f34978caf4819083f90eba4944d8e8 completed April 30, 2026, 12:22 p.m.
Created at: May 1, 2026, 1:39 a.m.