Triple
T14715261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abaqa’s mother (Ilkhanid consort) |
E345660
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 13th-century Mongol noblewoman |
C19943
|
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: 13th-century Mongol noblewoman Context triple: [Abaqa’s mother (Ilkhanid consort), instanceOf, 13th-century Mongol noblewoman]
-
A.
Mongol princess
chosen
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.
-
B.
Mongol empress consort
A Mongol empress consort is the principal wife of a Mongol khan or emperor, holding significant political, diplomatic, and domestic authority within the imperial court and broader empire.
-
C.
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.
-
D.
Mughal noblewoman
A Mughal noblewoman is an elite female member of the Mughal courtly aristocracy, distinguished by her lineage, wealth, political influence, and participation in the cultural and social life of the empire.
-
E.
11th-century noblewoman
An 11th-century noblewoman is a high-born female member of medieval European aristocracy whose life centers on managing estates, forging political alliances through marriage, and upholding social and religious obligations within a feudal hierarchy.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:29 a.m.