Triple
T36933919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dondogdulam |
E913559
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mongolian 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: Mongolian noblewoman Context triple: [Dondogdulam, instanceOf, Mongolian 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.
Tatar princess
A Tatar princess is a noblewoman of Tatar heritage, traditionally embodying the political influence, cultural refinement, and lineage of Tatar royal or aristocratic families.
-
D.
Mongol noble
A Mongol noble is a high-ranking member of Mongol society, typically belonging to ruling or aristocratic lineages, who holds political, military, and economic power within the Mongol Empire or its successor states.
-
E.
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.
- 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.