Triple
T23575155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SRD |
E580231
|
entity |
| Predicate | associatedStationFareZone |
P72429
|
FINISHED |
| Object | Glasgow Subway fare system |
—
|
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: Glasgow Subway fare system | Statement: [SRD, associatedStationFareZone, Glasgow Subway fare system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedStationFareZone Context triple: [SRD, associatedStationFareZone, Glasgow Subway fare system]
-
A.
adjacentFareZone
Indicates that two fare zones are directly next to each other, sharing a common boundary without any zones in between.
-
B.
fareZoneIncludes
Indicates that a specified fare zone geographically or logically contains a given location, stop, or segment for fare calculation purposes.
-
C.
hasFareZone
Indicates that an entity is located within or associated with a specific fare zone used for pricing or ticketing.
-
D.
hasFareZoneSystem
chosen
Indicates that an entity uses or is associated with a particular fare zone system for determining travel costs or ticketing.
-
E.
fareZoneDescription
Indicates the textual description of the fare zone associated with a service, location, or segment.
- 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_69e24601a9108190bc31e83833c980e4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1afd5a7e88190ba348d58e552bd3c |
completed | April 29, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:38 p.m.