Triple

T36384662
Position Surface form Disambiguated ID Type / Status
Subject Jalal ad-Din Mingburnu E896155 entity
Predicate instanceOf P0 FINISHED
Object Khwarazmian sultan C58772 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: Khwarazmian sultan
Context triple: [Jalal ad-Din Mingburnu, instanceOf, Khwarazmian sultan]
  • A. Khwarazmian ruler chosen
    A Khwarazmian ruler is a sovereign leader of the Khwarazmian dynasty who governed the historical region of Khwarazm, overseeing its political, military, and administrative affairs.
  • B. Ghaznavid sultan
    A Ghaznavid sultan is the sovereign ruler of the medieval Ghaznavid dynasty, governing its territories, directing military campaigns, and overseeing political, economic, and religious affairs of the state.
  • C. Khan of Bukhara
    The Khan of Bukhara is the sovereign ruler of the Khanate of Bukhara, a Central Asian polity historically centered in the city of Bukhara and exercising political, military, and religious authority over its territories.
  • D. Zengid ruler
    A Zengid ruler is a sovereign or governor from the Zengid dynasty, a 12th–13th century Muslim Turkic ruling house that controlled parts of Syria and northern Iraq, known for its military campaigns against Crusader states and efforts to unify Muslim territories.
  • E. Khan of Kokand
    The Khan of Kokand was the hereditary ruler of the Kokand Khanate in Central Asia, exercising political, military, and economic authority over the state and its subjects from the 18th to the late 19th century.
  • 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_69f76e51d358819092bbc5f119f49476 completed May 3, 2026, 3:48 p.m.
Created at: May 3, 2026, 4:10 p.m.