Triple
T19089334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seoul Station |
E467238
|
entity |
| Predicate | formerName |
P65
|
FINISHED |
| Object |
Gyeongseong Station
Gyeongseong Station was the former name of Seoul’s main railway station during the Japanese colonial period in Korea.
|
E1357826
|
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: Gyeongseong Station | Statement: [Seoul Station, formerName, Gyeongseong Station]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gyeongseong Station Context triple: [Seoul Station, formerName, Gyeongseong Station]
-
A.
Jagalchi Station
Jagalchi Station is a subway station in Busan, South Korea, serving the bustling Jagalchi Fish Market area and nearby downtown attractions.
-
B.
Samhung Station
Samhung Station is a stop on the Pyongyang Metro system in North Korea’s capital city.
-
C.
Jonu Station
Jonu Station is a stop on the Pyongyang Metro system in North Korea, serving passengers on one of the capital’s main urban rail lines.
-
D.
Yangjae Station
Yangjae Station is a major subway station in southern Seoul, South Korea, serving as an important transit hub on multiple lines within the city’s metro network.
-
E.
Kwangbok Station
Kwangbok Station is a stop on the Pyongyang Metro system in North Korea, serving passengers along one of the capital’s main underground transit lines.
- 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: Gyeongseong Station Triple: [Seoul Station, formerName, Gyeongseong Station]
Generated description
Gyeongseong Station was the former name of Seoul’s main railway station during the Japanese colonial period in Korea.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Gyeongseong Station Target entity description: Gyeongseong Station was the former name of Seoul’s main railway station during the Japanese colonial period in Korea.
-
A.
Jagalchi Station
Jagalchi Station is a subway station in Busan, South Korea, serving the bustling Jagalchi Fish Market area and nearby downtown attractions.
-
B.
Samhung Station
Samhung Station is a stop on the Pyongyang Metro system in North Korea’s capital city.
-
C.
Jonu Station
Jonu Station is a stop on the Pyongyang Metro system in North Korea, serving passengers on one of the capital’s main urban rail lines.
-
D.
Yangjae Station
Yangjae Station is a major subway station in southern Seoul, South Korea, serving as an important transit hub on multiple lines within the city’s metro network.
-
E.
Kwangbok Station
Kwangbok Station is a stop on the Pyongyang Metro system in North Korea, serving passengers along one of the capital’s main underground transit lines.
- 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e34981648190a89b006831846940 |
completed | April 20, 2026, 8:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a05dd90862881908e7cf95935847f8d |
completed | May 14, 2026, 2:34 p.m. |
| NEDg | Description generation | batch_6a05dfcd85b08190b0ec431590396dbb |
completed | May 14, 2026, 2:44 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a05e09c58308190975c69c86482292a |
completed | May 14, 2026, 2:47 p.m. |
Created at: April 10, 2026, 12:04 p.m.