Triple
T22847477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empress Longyu |
E566262
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Chinese royal 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: Chinese royal consort Context triple: [Empress Longyu, instanceOf, Chinese royal 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.
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.
-
C.
Joseon queen consort
A Joseon queen consort was the principal wife of the reigning king of the Korean Joseon dynasty, serving as the highest-ranking woman in the court with significant ceremonial, familial, and sometimes political responsibilities.
-
D.
concubine of the Japanese emperor
A concubine of the Japanese emperor was a woman of lower rank than the empress or official consorts who lived within the imperial court to bear children and support the emperor, often playing roles in court politics, culture, and succession.
-
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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:36 p.m.