Triple
T33400885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghiyath al-Din Muhammad |
E855294
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ilkhanid official |
C58259
|
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: Ilkhanid official Context triple: [Ghiyath al-Din Muhammad, instanceOf, Ilkhanid official]
-
A.
Timurid official
A Timurid official was an administrative or military functionary serving the Timurid Empire, responsible for implementing imperial policies, managing provincial governance, and maintaining order and revenue collection under the authority of the Timurid rulers.
-
B.
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.
-
C.
Seljuk official
A Seljuk official is an administrative or military functionary serving the Seljuk Empire, responsible for implementing state policies, managing governance, and maintaining order within the sultan’s domains.
-
D.
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.
-
E.
Timurid noble
A Timurid noble is a high-ranking aristocrat within the Timurid Empire, typically of Turco-Mongol lineage, who held land, military command, and administrative authority under the dynasty founded by Timur (Tamerlane).
- 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:35 a.m.