Triple

T33624230
Position Surface form Disambiguated ID Type / Status
Subject Jalal al-Din Masud Shah Inju E861355 entity
Predicate instanceOf P0 FINISHED
Object Injuid dynasty ruler C58275 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: Injuid dynasty ruler
Context triple: [Jalal al-Din Masud Shah Inju, instanceOf, Injuid dynasty ruler]
  • A. Injuid dynasty ruler chosen
    An Injuid dynasty ruler is a medieval Persian monarch from the Injuid family who governed parts of Fars and central Iran during the 14th century, overseeing political, military, and administrative affairs.
  • B. Manghit dynasty ruler
    A Manghit dynasty ruler is a sovereign from the Uzbek Manghit family who governed the Emirate of Bukhara, overseeing its political, military, and religious affairs from the mid-18th to early 20th centuries.
  • C. Aulikara dynasty ruler
    An Aulikara dynasty ruler is a monarch from the early medieval Indian Aulikara lineage, governing regions of central India and known primarily through inscriptions and historical records.
  • D. Zand dynasty ruler
    A Zand dynasty ruler is a monarch from the 18th-century Iranian Zand dynasty who governed parts of Iran, particularly from the capital Shiraz, between the fall of the Afsharids and the rise of the Qajars.
  • E. Samma dynasty ruler
    A Samma dynasty ruler is a sovereign who governed parts of Sindh and surrounding regions in present-day Pakistan between the 14th and 16th centuries under the Samma dynasty.
  • 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_69f34980fabc81909819228729a9ca84 completed April 30, 2026, 12:22 p.m.
Created at: May 1, 2026, 1:41 a.m.