Triple
T20688251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Onjo of Baekje |
E508479
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | legendary Korean king |
C18267
|
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: legendary Korean king Context triple: [Onjo of Baekje, instanceOf, legendary Korean king]
-
A.
Korean king
chosen
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.
King of Anshan
The "King of Anshan" is a conceptual class representing the sovereign ruler of the ancient Elamite city-state of Anshan, embodying political authority, territorial control, and dynastic legitimacy within that historical context.
-
D.
Shang dynasty king
A Shang dynasty king was the supreme political, military, and religious ruler of the Shang state, responsible for governing territories, leading armies, and conducting divination and ritual ceremonies to communicate with ancestors and deities.
-
E.
Goryeo dynasty person
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.
- 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_69e0b4c1ed408190b72dd26b1e33f8a1 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:45 a.m.