Triple
T32586477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empress Sunmyeonghyo |
E832935
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Korean empress consort |
C45445
|
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 consort Context triple: [Empress Sunmyeonghyo, instanceOf, Korean empress consort]
-
A.
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.
-
B.
Joseon queen consort
chosen
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.
-
C.
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.
-
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.
Song dynasty empress
A Song dynasty empress is the principal wife of a reigning Song emperor who holds the highest female rank in the imperial court, overseeing palace affairs, ritual duties, and often influencing political and familial succession matters.
- 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_69f34929ff648190aded9424aa7564ae |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:04 a.m.