Triple
T21868699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Wongyeong |
E539948
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Korean royal consort |
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 royal consort Context triple: [Queen Wongyeong, instanceOf, Korean royal consort]
-
A.
Chinese imperial consort
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.
Javanese royal consort
A Javanese royal consort is the spouse or recognized partner of a Javanese monarch, holding ceremonial, social, and sometimes political roles within the traditional Javanese court hierarchy.
-
C.
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.
-
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.
Great Royal Wife
The Great Royal Wife was the principal queen consort of an ancient Egyptian pharaoh, holding the highest status among royal women and often wielding significant political, religious, and ceremonial influence.
- F. None of above. chosen
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_69e0c478f59081909d54302b57fc1ce3 |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 6:57 p.m.