Triple
T2952781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LinkPass |
E79858
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transportation pass |
C11349
|
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 transportation pass Context triple: [LinkPass, instanceOf, public transportation pass]
-
A.
public transport ticket
chosen
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.
-
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 transit system
A public transit system is an organized network of shared transportation services—such as buses, trains, subways, and trams—designed to move large numbers of people efficiently within and between urban and regional areas.
-
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 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.
- 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_69ad8b1276588190a374a0b12e0f7bdf |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 2:57 p.m.