Triple

T8239917
Position Surface form Disambiguated ID Type / Status
Subject Kazan Khanate E192508 entity
Predicate instanceOf P0 FINISHED
Object successor state of the Golden Horde C12380 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: successor state of the Golden Horde
Context triple: [Kazan Khanate, instanceOf, successor state of the Golden Horde]
  • A. Mongol successor state chosen
    A Mongol successor state is a political entity that emerged from the fragmentation of the Mongol Empire, inheriting its territories, institutions, and ruling elites while developing distinct regional identities and governance structures.
  • B. Turco-Mongol
    Turco-Mongol refers to the historical synthesis of Turkic and Mongol political, military, and cultural traditions that shaped several Eurasian empires from the medieval to early modern periods.
  • C. Byzantine successor state
    A Byzantine successor state is a political entity that emerged from the fragmentation of the Byzantine Empire, claiming continuity with its imperial, cultural, and religious traditions.
  • D. successor state of the Western Roman Empire
    A successor state of the Western Roman Empire is a political entity that emerged in its former territories, inheriting and adapting Roman institutions, culture, and legal traditions while developing its own distinct identity.
  • E. successor state of the Western Roman Empire
    A successor state of the Western Roman Empire is a political entity that emerged in former Western Roman territories, inheriting and adapting Roman institutions, culture, and legal traditions while establishing its own distinct governance and identity.
  • 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_69ca82dc8f148190a2c75a98501a7b91 completed March 30, 2026, 2:04 p.m.
Created at: March 30, 2026, 5:47 p.m.