Triple
T16060986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noble Consort Yi |
E389610
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Qing dynasty noble 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 noble consort Context triple: [Noble Consort Yi, instanceOf, Qing dynasty noble 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.
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.
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.
-
D.
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.
-
E.
empress dowager
An empress dowager is the widow or mother of an emperor who often holds significant political influence or de facto power within an 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:57 a.m.