Triple

T28492682
Position Surface form Disambiguated ID Type / Status
Subject Safa Giray E721018 entity
Predicate instanceOf P0 FINISHED
Object ruler of Kazan Khanate C54127 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: ruler of Kazan Khanate
Context triple: [Safa Giray, instanceOf, ruler of Kazan Khanate]
  • A. Crimean khan
    A Crimean khan was the sovereign ruler of the Crimean Khanate, a Turkic-Mongol state that existed from the 15th to the 18th century under the suzerainty of the Ottoman Empire.
  • B. Aq Qoyunlu ruler
    An Aq Qoyunlu ruler is a sovereign leader of the Aq Qoyunlu tribal confederation who exercised political, military, and administrative authority over its territories in Anatolia, Iran, and surrounding regions during the 14th–16th centuries.
  • C. Timurid ruler
    A Timurid ruler is a sovereign from the Timurid dynasty (14th–16th centuries) who governed territories in Central Asia, Iran, and surrounding regions, often noted for military conquest, Persianate court culture, and patronage of arts and architecture.
  • D. Khan of Khiva
    The Khan of Khiva was the hereditary ruler of the Khanate of Khiva, a Central Asian polity centered in Khwarezm, who held political, military, and often religious authority over the region until its abolition in the early 20th century.
  • E. Great Horde ruler
    A Great Horde ruler is the sovereign leader of the post-Golden Horde polity, exercising supreme political, military, and administrative authority over its territories and nomadic subjects.
  • 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_69f01a5afdac8190ac6e72d5c100bd58 completed April 28, 2026, 2:24 a.m.
Created at: April 28, 2026, 3:02 a.m.