Triple

T16026986
Position Surface form Disambiguated ID Type / Status
Subject Afanasy Danilovich E388740 entity
Predicate instanceOf P0 FINISHED
Object member of the ruling house of Moscow C12793 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: member of the ruling house of Moscow
Context triple: [Afanasy Danilovich, instanceOf, member of the ruling house of Moscow]
  • A. member of the House of Romanov
    A member of the House of Romanov is an individual belonging by birth or marriage to the former imperial dynasty that ruled Russia from 1613 until the abdication of Tsar Nicholas II in 1917.
  • B. member of the Rurik dynasty chosen
    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. 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.
  • D. member of the House of Holstein-Gottorp-Romanov
    A member of the House of Holstein-Gottorp-Romanov is an individual belonging to the German-Russian dynastic branch that ruled the Russian Empire from Peter III through the last tsars, combining Holstein-Gottorp and Romanov lineage.
  • E. member of the Godunov family
    A member of the Godunov family is an individual belonging to a historically significant Russian noble lineage, often associated with political influence, landownership, and cultural heritage in Russia.
  • 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_69d86dada3808190825d5f80d72fbe88 completed April 10, 2026, 3:25 a.m.
Created at: April 10, 2026, 4:56 a.m.