Triple
T8177189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITX-Saemaeul |
E190965
|
entity |
| Predicate | serviceCategoryInKorailSystem |
P21523
|
FINISHED |
| Object | mid-range express |
—
|
LITERAL 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: mid-range express | Statement: [ITX-Saemaeul, serviceCategoryInKorailSystem, mid-range express]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceCategoryInKorailSystem Context triple: [ITX-Saemaeul, serviceCategoryInKorailSystem, mid-range express]
-
A.
railServiceType
chosen
Indicates the specific category or type of rail service that applies to the relationship between the involved entities (e.g., local, express, freight).
-
B.
railServicesTo
Indicates that rail transportation services operate from one location to another specified destination.
-
C.
railwayStationCategory
Indicates the classification or type category assigned to a railway station within a rail network or system.
-
D.
subwayServices
Indicates that one entity provides or operates subway transportation services for another entity or area.
-
E.
transportationServedBy
Indicates that a transportation facility, route, or area is provided service or coverage by a specific transportation provider or mode.
- F. None of above.
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_69ca82c1c0a08190bf8692b4d91a03ca |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4aba0dd88190828080d0d89612eb |
completed | March 31, 2026, 4:16 a.m. |
| PD | Predicate disambiguation | batch_69cb36a7952481908f34e3e82f375a84 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:40 p.m.