Triple
T18585538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | flat fare (Washington Metro) |
E454227
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fare policy |
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: fare policy Context triple: [flat fare (Washington Metro), instanceOf, fare policy]
-
A.
discount fare
A discount fare is a reduced-price ticket or rate offered under specific conditions, such as advance purchase, limited availability, or eligibility criteria, to encourage travel or purchase.
-
B.
fare card
A fare card is a reusable, often electronic, payment token used to access and pay for rides on public transportation systems.
-
C.
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.
-
D.
fare association
A fare association represents the defined relationship between multiple fare components, rules, or pricing conditions that together determine the total cost and applicability of a travel transaction.
-
E.
fare payment system
A fare payment system is a coordinated set of processes and technologies that calculates, collects, and validates payments for transportation services from passengers.
- 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.