Triple
T8031339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glasgow St Enoch railway station |
E186984
|
entity |
| Predicate | servedTraffic |
P16273
|
FINISHED |
| Object | passenger services |
—
|
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: passenger services | Statement: [Glasgow St Enoch railway station, servedTraffic, passenger services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedTraffic Context triple: [Glasgow St Enoch railway station, servedTraffic, passenger services]
-
A.
annualTraffic
Indicates the typical amount or volume of traffic associated with something over the course of a year.
-
B.
cargoTrafficRank
Indicates the relative position of an entity in an ordered list based on the volume or intensity of its cargo traffic.
-
C.
servesSeasonalTraffic
Indicates that an entity provides service only during specific seasons or periods of the year, rather than year-round.
-
D.
passengerTraffic
chosen
Indicates the flow or volume of passengers moving through or using a particular transport service, route, or facility.
-
E.
networkServed
Indicates that a network provides connectivity or services to a particular entity or set of entities.
- 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_69ca82ae2d1081909dbfee42b41db419 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3eef921081908d0ea21f142c175a |
completed | March 31, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69cb049688208190b32088bd2c5930bc |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:22 p.m.