Triple
T18585539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | flat fare (Washington Metro) |
E454227
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transit 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 transit pricing scheme Context triple: [flat fare (Washington Metro), instanceOf, public transit pricing scheme]
-
A.
public transport pricing scheme
chosen
A public transport pricing scheme is a structured set of rules and fares that determines how passengers are charged for using public transit services based on factors such as distance, time, mode, and user category.
-
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 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.
-
D.
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.
-
E.
public transit route
A public transit route is a predefined path with designated stops and schedules along which public transportation vehicles (such as buses, trams, or trains) operate to move passengers between locations.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:44 a.m.