Triple
T36933892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Dondogdulam |
E913558
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mongolian royal consort |
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: Mongolian royal consort Context triple: [Queen Dondogdulam, instanceOf, Mongolian royal consort]
-
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.
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.
-
C.
Burmese royal consort
A Burmese royal consort is a spouse or recognized partner of a Burmese monarch who holds an official courtly rank and ceremonial, political, or dynastic responsibilities within the royal household.
-
D.
Korean royal consort
A Korean royal consort is a woman of noble or selected status who becomes the king’s secondary wife or official concubine, holding recognized rank and influence within the royal court without being the primary queen.
-
E.
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.
- 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_69f76e896c988190880c130e01303dd4 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.