Triple

T33140515
Position Surface form Disambiguated ID Type / Status
Subject Василий Александрович E848134 entity
Predicate instanceOf P0 FINISHED
Object представитель владимиро-суздальской княжеской линии C12651 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: представитель владимиро-суздальской княжеской линии
Context triple: [Василий Александрович, instanceOf, представитель владимиро-суздальской княжеской линии]
  • A. Rurikid princely branch chosen
    A Rurikid princely branch is a dynastic line descending from the medieval Rurikid ruling family, typically associated with governance over a specific principality or territory in Kievan Rus’ and its successor states.
  • B. member of the Rurik dynasty
    A member of the Rurik dynasty is an individual belonging to the medieval ruling family traditionally traced to the Varangian prince Rurik, which governed parts of Eastern Europe, including Kievan Rus and later principalities, from the 9th to the 16th centuries.
  • C. Rurikid dynasty branch
    A Rurikid dynasty branch is a lineage subgroup descending from the medieval Rurikid ruling family, typically associated with a specific territory, princely title, and period of political influence in Eastern Europe.
  • D. member of the Dolgorukov family
    A member of the Dolgorukov family is an individual belonging to the historically prominent Russian noble house of Dolgorukov, known for its political influence, military service, and close ties to the ruling dynasties.
  • E. member of the House of Moscow
    A member of the House of Moscow is an individual belonging to a noble or ruling dynasty historically associated with governing and influencing the political, social, and cultural life of Moscow.
  • 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_69f3495961d88190b16ea542c2c5f825 completed April 30, 2026, 12:21 p.m.
Created at: May 1, 2026, 1:28 a.m.