Triple
T36519997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baqi Muhammad Khan |
E900151
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Janid dynasty ruler |
C62305
|
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: Janid dynasty ruler Context triple: [Baqi Muhammad Khan, instanceOf, Janid dynasty ruler]
-
A.
Sayyid dynasty ruler
A Sayyid dynasty ruler is a sovereign from the Sayyid lineage who governed parts of northern India during the early 15th century, claiming descent from the Prophet Muhammad and ruling primarily from Delhi.
-
B.
Arghun dynasty ruler
An Arghun dynasty ruler is a sovereign from the late medieval Turco-Mongol Arghun family who governed regions of present-day Afghanistan and Pakistan, particularly Sindh and parts of Baluchistan, often blending Persianate, Islamic, and Central Asian political traditions.
-
C.
Salian dynasty ruler
A Salian dynasty ruler is a medieval German king or Holy Roman Emperor from the Salian (Frankish) royal house who governed large parts of Central Europe between the early 11th and mid-12th centuries.
-
D.
Kart dynasty ruler
A Kart dynasty ruler is a medieval Islamic monarch from the Kart (Kurt) dynasty who governed the Herat-centered region of Khorasan, balancing local authority with shifting allegiances to larger imperial powers such as the Mongols and Timurids.
-
E.
Muzaffarid ruler
A Muzaffarid ruler is a sovereign or prince from the Muzaffarid dynasty that governed parts of Iran during the 14th century, exercising political, military, and administrative authority over its territories.
- 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_69f76e5eedb88190a393b8c623f71dd7 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:11 p.m.