Triple
T28571647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empress Myeongseong |
E723128
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Korean empress |
C45446
|
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: Korean empress Context triple: [Empress Myeongseong, instanceOf, Korean empress]
-
A.
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.
-
B.
Korean emperor
A Korean emperor is the supreme hereditary monarch who holds the highest sovereign authority over a unified Korean state, historically or in a conceptual context.
-
C.
Korean royal consort
chosen
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.
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.
-
E.
Empress of Japan
The Empress of Japan is the female consort or reigning sovereign of the Japanese imperial family, embodying ceremonial, cultural, and symbolic roles within the world’s oldest continuous hereditary monarchy.
- 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 4:10 a.m.