Triple
T23803940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ScotRail East Lothian area |
E589649
|
entity |
| Predicate | usedInTimetablesAndTickets |
P21407
|
FINISHED |
| Object | ScotRail fare tables |
—
|
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: ScotRail fare tables | Statement: [ScotRail East Lothian area, usedInTimetablesAndTickets, ScotRail fare tables]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInTimetablesAndTickets Context triple: [ScotRail East Lothian area, usedInTimetablesAndTickets, ScotRail fare tables]
-
A.
usedInRailwayTickets
Indicates that something is employed or applied in the context of railway tickets, such as their creation, validation, or usage.
-
B.
isUsedInTransportTimetables
chosen
Indicates that something is employed or referenced within transport timetables or schedules.
-
C.
usedForRailwayTimetables
Indicates that something is employed in the creation, organization, or presentation of railway timetables.
-
D.
usedBetweenStations
Indicates that something (such as a service, route, or resource) is utilized in the context of travel or operation between two stations.
-
E.
partOfFareStructure
Indicates that one element is included as a component within a larger fare structure or pricing scheme.
- 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_69e25d19fecc8190a5cf39bbb18d5d7f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c750048c8190899ff611df35b361 |
completed | April 29, 2026, 8:54 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:55 p.m.