Triple

T19425090
Position Surface form Disambiguated ID Type / Status
Subject Ilghazi E485960 entity
Predicate instanceOf P0 FINISHED
Object Turkoman ruler C40704 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: Turkoman ruler
Context triple: [Ilghazi, instanceOf, Turkoman ruler]
  • A. Turkic monarch
    A Turkic monarch is a sovereign ruler from a Turkic-speaking people or dynasty, typically holding titles such as khan, khagan, sultan, or bey, and exercising supreme political and military authority over a Turkic state or 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. Bactrian ruler
    A Bactrian ruler is a sovereign or governing authority who held political power over the ancient region of Bactria, typically during the Hellenistic or early Central Asian historical periods.
  • 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. Artuqid ruler chosen
    An Artuqid ruler is a sovereign or governor from the Artuqid dynasty, a Turkoman ruling family that controlled various principalities in Upper Mesopotamia and Anatolia between the late 11th and early 15th centuries.
  • 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_69d8e8d688f881909c85104a62e09d8a completed April 10, 2026, 12:11 p.m.
Created at: April 10, 2026, 1:37 p.m.