Triple
T24022292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Börte |
E594855
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | empress consort of the Mongol Empire |
C27380
|
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: empress consort of the Mongol Empire Context triple: [Börte, instanceOf, empress consort of the Mongol Empire]
-
A.
Mongol empress consort
chosen
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.
-
B.
Mughal empress consort
A Mughal empress consort is the principal wife of a reigning Mughal emperor, holding significant ceremonial status, political influence, and often patronage roles within the imperial court.
-
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.
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.
-
E.
Mughal empress
A Mughal empress is the principal wife or consort of a Mughal emperor, wielding varying degrees of political, cultural, and domestic influence within the imperial court of the Mughal Empire.
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 9:51 p.m.