Triple

T12526622
Position Surface form Disambiguated ID Type / Status
Subject Princess Aurora Pavlovna Demidova di San Donato E299455 entity
Predicate instanceOf P0 FINISHED
Object member of the Demidov family C31593 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 Demidov family
Context triple: [Princess Aurora Pavlovna Demidova di San Donato, instanceOf, member of the Demidov family]
  • A. 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.
  • B. member of the Tolstoy family
    A member of the Tolstoy family is an individual belonging by birth or marriage to the historically significant Russian noble lineage associated with the writer Leo Tolstoy and his relatives.
  • C. member of the Shuisky family
    A member of the Shuisky family is an individual belonging to the powerful Russian noble lineage that played significant political and dynastic roles, particularly during the late Rurikid and Time of Troubles periods.
  • D. 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.
  • E. 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.
  • F. None of above. chosen

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_69d6ada5cdd48190860d9ce30aff69be completed April 8, 2026, 7:33 p.m.
Created at: April 8, 2026, 9:57 p.m.