Triple
T19117055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gimpo Goldline |
E467932
|
entity |
| Predicate | hasStation |
P35
|
FINISHED |
| Object |
Bulsan station
Bulsan station is a metro station on the Gimpo Goldline serving passengers in Gimpo, South Korea.
|
E1400223
|
NE FINISHED |
How this triple was built (4 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: Bulsan station | Statement: [Gimpo Goldline, hasStation, Bulsan station]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bulsan station Context triple: [Gimpo Goldline, hasStation, Bulsan station]
-
A.
Sasang Station
Sasang Station is a major railway and subway interchange in Busan, South Korea, serving as a key transit hub for both local and intercity travel.
-
B.
Beomgye Station
Beomgye Station is a subway station in Anyang, South Korea, serving as a local transit hub on the Seoul metropolitan rail network.
-
C.
Dongsu Station
Dongsu Station is a major subway station in Incheon, South Korea, serving as an important transit hub within the city's metro network.
-
D.
Miryang Station
Miryang Station is a major railway station in Miryang, South Korea, serving as an important junction on the country’s rail network.
-
E.
Bongcheon Station
Bongcheon Station is a subway station on Seoul Subway Line 2 serving the Bongcheon-dong area in Seoul, South Korea.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Bulsan station Triple: [Gimpo Goldline, hasStation, Bulsan station]
Generated description
Bulsan station is a metro station on the Gimpo Goldline serving passengers in Gimpo, South Korea.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Bulsan station Target entity description: Bulsan station is a metro station on the Gimpo Goldline serving passengers in Gimpo, South Korea.
-
A.
Sasang Station
Sasang Station is a major railway and subway interchange in Busan, South Korea, serving as a key transit hub for both local and intercity travel.
-
B.
Beomgye Station
Beomgye Station is a subway station in Anyang, South Korea, serving as a local transit hub on the Seoul metropolitan rail network.
-
C.
Dongsu Station
Dongsu Station is a major subway station in Incheon, South Korea, serving as an important transit hub within the city's metro network.
-
D.
Miryang Station
Miryang Station is a major railway station in Miryang, South Korea, serving as an important junction on the country’s rail network.
-
E.
Bongcheon Station
Bongcheon Station is a subway station on Seoul Subway Line 2 serving the Bongcheon-dong area in Seoul, South Korea.
- F. None of above. chosen
Provenance (5 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e399a6d8819090a9501ff1637b9d |
completed | April 20, 2026, 8:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a07dba9ca90819093aed4141d589d58 |
completed | May 16, 2026, 2:51 a.m. |
| NEDg | Description generation | batch_6a07dd4080a48190adc444976042bfa8 |
completed | May 16, 2026, 2:58 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a07de09b21c8190a9743ee145a3d9b7 |
completed | May 16, 2026, 3:01 a.m. |
Created at: April 10, 2026, 12:05 p.m.