Triple
T12057674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinuiju |
E287083
|
entity |
| Predicate | borders |
P224
|
FINISHED |
| Object | Dandong |
E301373
|
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: Dandong | Statement: [Sinuiju, borders, Dandong]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dandong Context triple: [Sinuiju, borders, Dandong]
-
A.
Dandong
chosen
Dandong is a northeastern Chinese border city on the Yalu River, known as a key gateway for trade and transport between China and North Korea.
-
B.
Tieling
Tieling is a prefecture-level city in northeastern China known for its coal resources and location within Liaoning Province.
-
C.
Yingkou
Yingkou is a coastal port city in northeastern China’s Liaoning Province, known as an important industrial and shipping hub on the Bohai Sea.
-
D.
Panjin
Panjin is an industrial and oil-producing city in northeastern China, best known for its striking Red Beach wetlands along the Bohai Sea.
-
E.
Liaoyuan
Liaoyuan is a prefecture-level city in northeastern China known for its coal mining history and location in the central part of Jilin Province.
- 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_69d6ab4780948190bdb9f7620c2ac27e |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9043bf0ec8190a51ef2641808320c |
completed | April 10, 2026, 2:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f49dea043c8190a74ffb448bbae5d0 |
completed | May 1, 2026, 12:34 p.m. |
Created at: April 8, 2026, 9:47 p.m.