Triple
T20557004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jinju Station |
E504744
|
entity |
| Predicate | connectsTo |
P845
|
FINISHED |
| Object | Mokpo |
—
|
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: Mokpo | Statement: [Jinju Station, connectsTo, Mokpo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mokpo Context triple: [Jinju Station, connectsTo, Mokpo]
-
A.
Mokpo
chosen
Mokpo is a coastal city in South Jeolla Province, South Korea, known as a regional transportation hub and gateway to numerous nearby islands.
-
B.
Gangjin
Gangjin is a coastal county and town in South Jeolla Province, South Korea, known for its historic celadon pottery kilns and scenic rural landscapes.
-
C.
Gwangyang
Gwangyang is an industrial port city in South Korea known for its major steelworks complex and scenic coastal and mountainous landscapes.
-
D.
Jeongeup
Jeongeup is a city in South Korea known for its location in North Jeolla Province and its cultural and historical heritage.
-
E.
Gunsan
Gunsan is a coastal city in North Jeolla Province, South Korea, known for its port, industrial facilities, and longstanding association with nearby military air operations.
- 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_69e0b4b6587c8190aee63dc7cff244ea |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a5de9c008190b8620628fb285e90 |
completed | April 20, 2026, 10:17 p.m. |
Created at: April 16, 2026, 11:38 a.m.