Triple
T2952780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LinkPass |
E79858
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transit fare product |
C13844
|
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: transit fare product Context triple: [LinkPass, instanceOf, transit fare product]
-
A.
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.
-
B.
public transit fare card
A public transit fare card is a reusable, stored-value or pass-based card that riders use to pay for access to buses, trains, and other public transportation services.
-
C.
public transport fare zone
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.
-
D.
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.
-
E.
public transport ticket
A public transport ticket is a proof-of-payment token, physical or digital, that grants an individual the right to use specified public transportation services for a defined route, time period, or fare zone.
- 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_69ad8b1276588190a374a0b12e0f7bdf |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 2:57 p.m.