Triple
T15321344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umid Bega Begum |
E366297
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Timurid noblewoman |
C12554
|
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: Timurid noblewoman Context triple: [Umid Bega Begum, instanceOf, Timurid noblewoman]
-
A.
Timurid princess
chosen
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.
-
B.
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.
-
C.
Ilkhanid consort
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.
-
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.
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.
- 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:16 a.m.