Triple
T33584904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hajji Khatun |
E860252
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ilkhanate noblewoman |
C35066
|
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 noblewoman Context triple: [Hajji Khatun, instanceOf, Ilkhanate noblewoman]
-
A.
Ilkhanid consort
chosen
An Ilkhanid consort is a royal spouse or favored partner of a ruler of the Ilkhanate, holding a significant position within the Mongol-Persian imperial court in the 13th–14th centuries.
-
B.
Timurid princess
A Timurid princess is a noblewoman of the Timurid dynasty, typically involved in dynastic politics, cultural patronage, and the consolidation of power across Central and South Asia between the 14th and 16th centuries.
-
C.
Mongol princess
A Mongol princess is a high-born woman of the Mongol imperial or noble lineage, whose status, marriages, and political alliances significantly influence tribal unity, diplomacy, and succession within the Mongol realm.
-
D.
Timurid royal consort
A Timurid royal consort is a spouse or principal partner of a Timurid ruler who played key roles in dynastic alliances, court politics, and the cultural life of the Timurid Empire.
-
E.
Shahbanu of Iran
The Shahbanu of Iran was the title given to the empress consort of the Shah, serving as the highest-ranking woman in the Iranian monarchy with ceremonial, cultural, and sometimes philanthropic roles.
- 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_69f3497e70e48190951c94d072879bec |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:40 a.m.