Triple

T3332722
Position Surface form Disambiguated ID Type / Status
Subject Grand Duchy of Vladimir E70069 entity
Predicate instanceOf P0 FINISHED
Object medieval East Slavic principality 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: medieval East Slavic principality
Context triple: [Grand Duchy of Vladimir, instanceOf, medieval East Slavic principality]
  • 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. East Slavic polity
    An East Slavic polity is a historically or contemporarily organized political entity—such as a state, principality, or federation—primarily inhabited and shaped by East Slavic peoples and their cultural, linguistic, and religious traditions.
  • D. 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).
  • E. South Slavic state
    A South Slavic state is a political entity whose core population, culture, and historical development are primarily associated with the South Slavic peoples of the Balkan Peninsula.
  • 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_69ad85a24f208190bcf83131bfed3521 completed March 8, 2026, 2:20 p.m.
Created at: March 8, 2026, 3:12 p.m.