Triple
T1710901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Busan Metro |
E36979
|
entity |
| Predicate | connectsTo |
P845
|
FINISHED |
| Object | Busan Station |
E36550
|
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: Busan Station | Statement: [Busan Metro, connectsTo, Busan Station]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Busan Station Context triple: [Busan Metro, connectsTo, Busan Station]
-
A.
Busan Station
chosen
Busan Station is a major railway hub in Busan, South Korea, serving high-speed KTX trains and regional services as one of the country’s key transportation centers.
-
B.
Yeonsan Station
Yeonsan Station is a major transit hub in Busan, South Korea, serving as an important interchange point on the city’s subway network.
-
C.
Daejeon Station
Daejeon Station is a major railway hub in central South Korea, serving high-speed KTX trains and connecting Daejeon to key cities nationwide.
-
D.
Seodaejeon Station
Seodaejeon Station is a major railway station in Daejeon, South Korea, serving as an important stop on national rail lines including high-speed services.
-
E.
Beomeosa Station
Beomeosa Station is a subway station in Busan, South Korea, serving as a key access point to the nearby Beomeosa Temple and surrounding Geumjeong District area.
- 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_69a88617439c819094ffb5d16a0f6307 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa63149288819082e7055d0d292d1d |
completed | March 6, 2026, 5:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adeac88e488190aeb6e7a1063405b7 |
completed | March 8, 2026, 9:31 p.m. |
Created at: March 4, 2026, 7:30 p.m.