Triple
T6688063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daejeon Station |
E152149
|
entity |
| Predicate | serves |
P98
|
FINISHED |
| Object | KTX |
E197067
|
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: KTX | Statement: [Daejeon Station, serves, KTX]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KTX Context triple: [Daejeon Station, serves, KTX]
-
A.
KTX
chosen
KTX is South Korea’s high-speed rail service that connects major cities such as Seoul and Busan.
-
B.
Korail
Korail is South Korea's national railroad operator, managing the country's major passenger and freight rail services.
-
C.
ITX-Saemaeul
ITX-Saemaeul is a class of South Korean intercity express trains operated by Korail, offering faster and more comfortable service than conventional trains on major routes.
-
D.
Gyeongbu High-Speed Railway
The Gyeongbu High-Speed Railway is South Korea’s primary high-speed rail corridor, linking Seoul and Busan and serving as a backbone of national passenger transport.
-
E.
K train
The K train was a former New York City Subway service designation that operated on parts of the Brooklyn–Manhattan Transit (BMT) system before being discontinued.
- 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_69c687f9977c819097e7f5ada4fe522e |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6b14e58708190a4ba8ff1c085f160 |
completed | March 27, 2026, 4:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c723b8a5288190a2fb4d956f2dc385 |
completed | March 28, 2026, 12:41 a.m. |
Created at: March 27, 2026, 2:04 p.m.