Triple
T12620811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dandong |
E301373
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Sinuiju |
E287083
|
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: Sinuiju | Statement: [Dandong, adjacentTo, Sinuiju]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sinuiju Context triple: [Dandong, adjacentTo, Sinuiju]
-
A.
Sinuiju, Korea
chosen
Sinuiju, Korea is a North Korean city on the Yalu River bordering China, known as an important industrial and transportation hub.
-
B.
Wonsan
Wonsan is a port city on North Korea’s east coast, known for its strategic military importance and role as a regional transportation and industrial hub.
-
C.
Kim Chaek City
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.
Nampo
Nampo is a major port city in southwestern North Korea, known for its industrial facilities and strategic location on the Yellow 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d960c75c9c819092265ebc2b39f21d |
completed | April 10, 2026, 8:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f65ed6f79881908872c644a9789f04 |
completed | May 2, 2026, 8:30 p.m. |
Created at: April 9, 2026, 5:13 p.m.