Triple
T10905549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metrolink fare zones |
E257559
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transport pricing scheme |
C28540
|
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 pricing scheme Context triple: [Metrolink fare zones, instanceOf, public transport pricing scheme]
-
A.
road pricing scheme
A road pricing scheme is a system for charging drivers fees to use specific roads or areas, typically to manage congestion, reduce environmental impacts, or fund transportation infrastructure.
-
B.
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.
-
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.
public transit plan
A public transit plan is a structured strategy that outlines routes, schedules, resources, and policies to provide efficient, accessible, and sustainable transportation services within a community or region.
-
E.
public transport ticketing system
A public transport ticketing system manages the purchase, validation, and tracking of fares and passes for passengers across various transit services.
- F. None of above. chosen
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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:22 p.m.