Triple
T34614090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Noble Consort Jingmu |
E888814
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Qing dynasty imperial consort |
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 imperial consort Context triple: [Imperial Noble Consort Jingmu, instanceOf, Qing dynasty imperial consort]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
Vietnamese empress consort
A Vietnamese empress consort is the principal wife of a reigning Vietnamese emperor, holding the highest female rank in the imperial court and often wielding significant political and ceremonial influence.
-
E.
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.
- 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_69f349d584e08190b40b9f6281ad50c4 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:03 a.m.