Triple
T19397031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colindale Underground station |
E485217
|
entity |
| Predicate | servesTravelcardZone |
P844
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Colindale Underground station, servesTravelcardZone, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesTravelcardZone Context triple: [Colindale Underground station, servesTravelcardZone, 4]
-
A.
locatedInTravelcardZoneBoundary
Indicates that something lies on or within the defined boundary of a specific travelcard fare zone.
-
B.
fareZoneIncludes
Indicates that a specified fare zone geographically or logically contains a given location, stop, or segment for fare calculation purposes.
-
C.
fareZoneFromCentralLondon
Indicates the public transport fare zone in which a location lies, measured relative to central London.
-
D.
hasFareZone
chosen
Indicates that an entity is located within or associated with a specific fare zone used for pricing or ticketing.
-
E.
isWithinLondonFareSystem
Indicates that an entity (such as a station, stop, or route) is located inside the area covered by the London public transport fare system.
- 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62573f5788190a635b92121db2cf7 |
completed | April 20, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:36 p.m.