Triple
T34067477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qaitmish Khatun |
E873666
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ilkhanate noble |
C35181
|
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: Ilkhanate noble Context triple: [Qaitmish Khatun, instanceOf, Ilkhanate noble]
-
A.
Mongol noble
chosen
A Mongol noble is a high-ranking member of Mongol society, typically belonging to ruling or aristocratic lineages, who holds political, military, and economic power within the Mongol Empire or its successor states.
-
B.
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).
-
C.
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.
-
D.
Ilkhanid official
An Ilkhanid official was an administrative or bureaucratic functionary serving the Ilkhanate (a Mongol-ruled dynasty in Iran and surrounding regions, 13th–14th centuries), responsible for implementing state policies, managing finances, justice, or provincial governance within the empire’s complex multiethnic administration.
-
E.
Afghan noble
An Afghan noble is a high-ranking member of Afghanistan’s traditional aristocracy, typically possessing hereditary titles, land, and social influence within tribal or urban elite structures.
- 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_69f349a4af208190afa14888f9c9fb9d |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:52 a.m.