Triple
T25603983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Ruislip |
E641858
|
entity |
| Predicate | isTravelcardZoneBoundary |
P105131
|
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: [West Ruislip, isTravelcardZoneBoundary, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTravelcardZoneBoundary Context triple: [West Ruislip, isTravelcardZoneBoundary, yes]
-
A.
locatedInTravelcardZoneBoundary
Indicates that something lies on or within the defined boundary of a specific travelcard fare zone.
-
B.
hasBorderRailwayStationWith
Indicates that two regions share a common border at which there is a railway station connecting or serving both sides.
-
C.
hasFareBoundary
chosen
Indicates that there is a defined limit or border beyond which a particular fare, ticket, or pricing rule no longer applies.
-
D.
fareZoneFromCentralLondon
Indicates the public transport fare zone in which a location lies, measured relative to central London.
-
E.
fareZoneOfStationIdentified
Indicates that the specific fare zone associated with a given station has been identified.
- 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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f9a89830819083b11f0b818e538d |
completed | May 2, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 4:37 p.m.