Triple
T20930723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamīn al-Dawla Abū al-Qāsim Maḥmūd ibn Sebüktegīn |
E515462
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ghaznavid ruler |
C37709
|
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: Ghaznavid ruler Context triple: [Yamīn al-Dawla Abū al-Qāsim Maḥmūd ibn Sebüktegīn, instanceOf, Ghaznavid ruler]
-
A.
Ghaznavid sultan
chosen
A Ghaznavid sultan is the sovereign ruler of the medieval Ghaznavid dynasty, governing its territories, directing military campaigns, and overseeing political, economic, and religious affairs of the state.
-
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.
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.
-
E.
ruler of Herat
A ruler of Herat is the sovereign authority who governs the city and region of Herat, overseeing its political, military, economic, and cultural affairs.
- 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_69e0b4fb431c8190b9d40e6a72f0cc87 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:49 p.m.