Triple
T13126013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Gongmin |
E311845
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ruler of Goryeo |
C25221
|
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: ruler of Goryeo Context triple: [Emperor Gongmin, instanceOf, ruler of Goryeo]
-
A.
Korean king
A Korean king is the sovereign ruler of a Korean dynasty, responsible for governing the kingdom, upholding Confucian ideals, overseeing military and diplomatic affairs, and serving as the symbolic and political head of state.
-
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.
Goryeo dynasty person
chosen
A Goryeo dynasty person is an individual who lived in or was significantly associated with Korea’s Goryeo dynasty (918–1392), contributing to its political, social, cultural, or historical developments.
-
D.
Jurchen chieftain
A Jurchen chieftain is a hereditary or militarily ascendant leader of a Jurchen tribal group who exercises political, military, and economic authority within the broader context of Northeast Asian steppe-forest societies.
-
E.
Manghit dynasty ruler
A Manghit dynasty ruler is a sovereign from the Uzbek Manghit family who governed the Emirate of Bukhara, overseeing its political, military, and religious affairs from the mid-18th to early 20th centuries.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:07 p.m.