Triple
T19449578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Seonjo of Joseon |
E486577
|
entity |
| Predicate | burialPlace |
P196
|
FINISHED |
| Object | Mokneung |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Mokneung | Statement: [King Seonjo of Joseon, burialPlace, Mokneung]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mokneung Context triple: [King Seonjo of Joseon, burialPlace, Mokneung]
-
A.
Mokneung
chosen
Mokneung is one of the royal burial sites from Korea’s Joseon Dynasty, forming part of the UNESCO-listed Royal Tombs complex.
-
B.
Mungyeong
Mungyeong is a city in South Korea known for its historic mountain passes, scenic hiking trails, and traditional cultural heritage.
-
C.
Gwangmyeong
Gwangmyeong is a city in South Korea known for its proximity to Seoul and attractions like the Gwangmyeong Cave, a former mine turned cultural and tourism complex.
-
D.
Jeongeup
Jeongeup is a city in South Korea known for its location in North Jeolla Province and its cultural and historical heritage.
-
E.
Tancheon
Tancheon is a river in South Korea that flows through the city of Seongnam and serves as a key urban waterway and recreational area.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 batches)
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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6338caeb48190aeb1d511996984e3 |
completed | April 20, 2026, 2:09 p.m. |
Created at: April 10, 2026, 1:38 p.m.