Triple
T19578273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wanggeom-seong |
E489918
|
entity |
| Predicate | transliteratedAs |
P5923
|
FINISHED |
| Object | Wanggŏmsŏng |
—
|
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: Wanggŏmsŏng | Statement: [Wanggeom-seong, transliteratedAs, Wanggŏmsŏng]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wanggŏmsŏng Context triple: [Wanggeom-seong, transliteratedAs, Wanggŏmsŏng]
-
A.
Pakchon
Pakchon is a city in North Pyongan Province, North Korea, known as a regional center for agriculture and light industry.
-
B.
Seogwipo
Seogwipo is a coastal city on South Korea’s Jeju Island known for its waterfalls, volcanic landscapes, and popular tourist attractions.
-
C.
Taebong
chosen
Taebong was a short-lived Korean kingdom of the early 10th century that emerged during the Later Three Kingdoms period before being absorbed by Goryeo.
-
D.
Sanggyeong
Sanggyeong was the principal royal capital city of the Balhae kingdom, serving as its political and cultural center in Northeast Asia.
-
E.
Hwaseong
Hwaseong is a city in Gyeonggi Province, South Korea, known for its rapid industrial growth and proximity to major urban centers like Suwon and Seoul.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6402693d88190a828c0e136895783 |
completed | April 20, 2026, 3:03 p.m. |
Created at: April 10, 2026, 1:42 p.m.