Triple
T33891012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Acton tube station |
E868763
|
entity |
| Predicate | isInFareZoneBoundary |
P105131
|
FINISHED |
| Object | between Zone 2 and Zone 3 |
—
|
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: between Zone 2 and Zone 3 | Statement: [North Acton tube station, isInFareZoneBoundary, between Zone 2 and Zone 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInFareZoneBoundary Context triple: [North Acton tube station, isInFareZoneBoundary, between Zone 2 and Zone 3]
-
A.
hasFareBoundary
chosen
Indicates that there is a defined limit or border beyond which a particular fare, ticket, or pricing rule no longer applies.
-
B.
hasFareZone
Indicates that an entity is located within or associated with a specific fare zone used for pricing or ticketing.
-
C.
fareZoneIncludes
Indicates that a specified fare zone geographically or logically contains a given location, stop, or segment for fare calculation purposes.
-
D.
isWithinFareSystem
Indicates that one transportation service, route, or area operates under and is covered by a specified fare or ticketing system.
-
E.
hasFareZoneCode
Indicates that an entity is associated with a specific fare zone identifier used for pricing or tariff purposes.
- 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_69f34996761c8190864e42f7c9cf215b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:48 a.m.