Triple
T17091549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Hamgyong Province |
E414737
|
entity |
| Predicate | hasPortCity |
P2745
|
FINISHED |
| Object | Kimchaek |
E418537
|
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: Kimchaek | Statement: [North Hamgyong Province, hasPortCity, Kimchaek]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kimchaek Context triple: [North Hamgyong Province, hasPortCity, Kimchaek]
-
A.
Phyongwon
Phyongwon is a city in North Korea known as an administrative and agricultural center within North Pyongan Province.
-
B.
Nyongbyon
Nyongbyon is a North Korean city best known internationally as the site of the country’s main nuclear research and reactor complex.
-
C.
Kim Chaek City
chosen
Kim Chaek City is an industrial port city in North Hamgyong Province, North Korea, named in honor of the Korean War general and politician Kim Chaek.
-
D.
Kyongsong
Kyongsong is a coastal town and county-level city in northeastern North Korea known for its hot springs and location along the Sea of Japan (East Sea).
-
E.
Nampo-dong
Nampo-dong is a bustling commercial and shopping district in central Busan, South Korea, known for its markets, street food, and proximity to the city’s harbor.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbfa09b08190be4303dd0d174feb |
completed | April 18, 2026, 7:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a015fbe1d4c81909ce7e4626516b51d |
completed | May 11, 2026, 4:49 a.m. |
Created at: April 10, 2026, 5:35 a.m.