Triple
T34513235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shah Shoja |
E886079
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Muzaffarid ruler |
C58771
|
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: Muzaffarid ruler Context triple: [Shah Shoja, instanceOf, Muzaffarid ruler]
-
A.
Muzaffarid ruler
chosen
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.
-
B.
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.
-
C.
Afsharid ruler
An Afsharid ruler is a sovereign belonging to the Afsharid dynasty that governed Iran and surrounding regions in the 18th century, exercising political, military, and administrative authority over its territories.
-
D.
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.
-
E.
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.
- 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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:01 a.m.