Triple
T38291971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Gongwon of the Namyang Hong clan |
E1022383
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Korean noblewoman |
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 noblewoman Context triple: [Queen Gongwon of the Namyang Hong clan, instanceOf, Korean noblewoman]
-
A.
Korean princess
A Korean princess is a royal female member of Korea’s monarchy, traditionally embodying noble lineage, cultural refinement, and responsibilities in courtly, diplomatic, and ceremonial life.
-
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
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.
-
D.
ancient Japanese noblewoman
An ancient Japanese noblewoman is an aristocratic lady of the imperial court, distinguished by her refined education, elaborate dress such as layered kimono, and participation in the political, literary, and ceremonial life of classical Japan.
-
E.
legendary Japanese empress consort
A legendary Japanese empress consort is a mythic or semi-historical imperial wife in Japan’s early chronicles, often credited with extraordinary virtues, political influence, or supernatural associations that shaped foundational narratives of the imperial line.
- 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_69f76df190f081908d5aa02c8a9286d0 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.