Triple
T33624231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jalal al-Din Masud Shah Inju |
E861355
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 14th-century Iranian ruler |
C58388
|
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: 14th-century Iranian ruler Context triple: [Jalal al-Din Masud Shah Inju, instanceOf, 14th-century Iranian ruler]
-
A.
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.
-
B.
Timurid ruler
A Timurid ruler is a sovereign from the Timurid dynasty (14th–16th centuries) who governed territories in Central Asia, Iran, and surrounding regions, often noted for military conquest, Persianate court culture, and patronage of arts and architecture.
-
C.
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.
-
D.
Ilkhan of the Ilkhanate
The Ilkhan of the Ilkhanate is the sovereign ruler of the Mongol-founded Ilkhanate in Persia, exercising supreme political, military, and administrative authority over its territories and vassals.
-
E.
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.
- 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_69f34980fabc81909819228729a9ca84 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:41 a.m.