Triple
T13295444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Travelcard Zones 1–5 |
E316668
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transport fare zone system |
C2855
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: public transport fare zone system Context triple: [Travelcard Zones 1–5, instanceOf, public transport fare zone system]
-
A.
public transport fare zone
chosen
A public transport fare zone is a defined geographic area within a transit network used to calculate ticket prices and validate passenger fares based on the zones they travel through.
-
B.
fare network
A fare network is an interconnected system of transportation routes, services, and pricing structures through which passengers can travel using coordinated tickets or payment methods.
-
C.
public transit fare payment system
A public transit fare payment system manages the calculation, collection, validation, and tracking of passenger payments across various transit services and media (e.g., cards, mobile apps, tickets) to authorize and record travel.
-
D.
transit fare product
A transit fare product is a purchasable medium (such as a ticket, pass, or stored value) that grants a rider the right to access and use public transportation services under specified conditions.
-
E.
commuter rail zone
A commuter rail zone is a designated geographic area used to determine fares, ticketing, and service boundaries for regional passenger rail travel.
- F. None of above.
Provenance (1 batch)
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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:28 p.m.