Triple
T18364937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empress Xiaoyichun |
E440018
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Qing dynasty noblewoman |
C33085
|
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: Qing dynasty noblewoman Context triple: [Empress Xiaoyichun, instanceOf, Qing dynasty noblewoman]
-
A.
consort of the Qianlong Emperor
A consort of the Qianlong Emperor is a woman who held an official rank within the imperial harem of the Qing dynasty, serving as one of the emperor’s recognized wives or concubines with defined status, duties, and privileges at the Qing court.
-
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.
Chinese imperial consort
chosen
A Chinese imperial consort is a woman who, ranked below the empress, belongs to the emperor’s harem and holds an officially defined status, title, and role within the hierarchical structure of the imperial court.
-
D.
Qing dynasty prince
A Qing dynasty prince is a male member of the imperial Aisin Gioro clan who holds a hereditary noble title within the hierarchical peerage system of the Qing Empire, often bearing political, military, or ceremonial responsibilities.
-
E.
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.
- 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_69d8b918221c8190a9f7b563d64ac677 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:38 a.m.