Triple
T20049376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dunbar railway station |
E499150
|
entity |
| Predicate | hasTimetabledInterCityServices |
P75704
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Dunbar railway station, hasTimetabledInterCityServices, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimetabledInterCityServices Context triple: [Dunbar railway station, hasTimetabledInterCityServices, yes]
-
A.
operatesInterCityServices
Indicates that an entity runs or provides transportation services connecting different cities.
-
B.
hasTimetabledServices
chosen
Indicates that scheduled or timetabled services are provided or operate in relation to the referenced entity.
-
C.
hasNightTrainService
Indicates that a transportation route or station is served by trains that operate during nighttime hours.
-
D.
hasCommuterServices
Indicates that a location or facility provides transportation services specifically intended for regular commuters, such as daily or frequent travelers between home and work or school.
-
E.
hasNationalRailService
Indicates that a place or facility is served by a country's national rail transportation network.
- 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6632cccb481908278c8b2930a8c26 |
completed | April 20, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:37 p.m.