Triple
T23408044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamhung |
E559987
|
entity |
| Predicate | alternativeName |
P39
|
FINISHED |
| Object | Hamhŭ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: Hamhŭng | Statement: [Hamhung, alternativeName, Hamhŭng]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hamhŭng Context triple: [Hamhung, alternativeName, Hamhŭng]
-
A.
Munhwaŏ
Munhwaŏ is the standardized form of the Korean language used in North Korea, based primarily on the Pyongyang dialect.
-
B.
Yŏngnŭng
Yŏngnŭng is the McCune–Reischauer romanization of Yeongneung, a royal tomb site in Paju, South Korea.
-
C.
Chŏngjŏn
Chŏngjŏn is the McCune–Reischauer romanization of the Korean name Jeongjeon, commonly referring to the main hall of the Jongmyo royal ancestral shrine in Seoul.
-
D.
Hamhung
chosen
Hamhung is a major city in northeastern North Korea, known as an important industrial center and for its distinctive style of cold noodle dish, Hamhung naengmyeon.
-
E.
Chosŏn Chikŏp Ch’ongdongmaeng
Chosŏn Chikŏp Ch’ongdongmaeng is the state-controlled national trade union federation in North Korea, closely aligned with the ruling Workers’ Party of Korea.
- 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a50f3f90819084fb682597fee1e1 |
completed | April 29, 2026, 6:28 a.m. |
Created at: April 17, 2026, 5:38 p.m.