Triple
T6995703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miryang |
E162206
|
entity |
| Predicate | romanizationRevised |
P23170
|
FINISHED |
| Object | Miryang-si |
E162206
|
NE FINISHED |
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: Miryang-si | Statement: [Miryang, romanizationRevised, Miryang-si]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Miryang-si Context triple: [Miryang, romanizationRevised, Miryang-si]
-
A.
Miryang
chosen
Miryang is a city in South Gyeongsang Province, South Korea, known for its scenic river valley setting, historical sites, and role as a regional transport and educational hub.
-
B.
Mungyeong
Mungyeong is a city in South Korea known for its historic mountain passes, scenic hiking trails, and traditional cultural heritage.
-
C.
Mokneung
Mokneung is one of the royal burial sites from Korea’s Joseon Dynasty, forming part of the UNESCO-listed Royal Tombs complex.
-
D.
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.
-
E.
Geumwang-eup
Geumwang-eup is a town-level administrative division in Eumseong County, located in North Chungcheong Province, South Korea.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69c68857ffc08190857dc62cd5253777 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbec259c8190bb4cfbc1ff6fc786 |
completed | March 27, 2026, 7:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7cbbd30e48190bbd75c8c442fea5a |
completed | March 28, 2026, 12:38 p.m. |
Created at: March 27, 2026, 2:32 p.m.