Triple
T22669405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarifverbund Nordwestschweiz |
E559881
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | integrated fare network |
C12710
|
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: integrated fare network Context triple: [Tarifverbund Nordwestschweiz, instanceOf, integrated fare network]
-
A.
fare network
chosen
A fare network is an interconnected system of transportation routes, services, and pricing structures through which passengers can travel using coordinated tickets or payment methods.
-
B.
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.
-
C.
commuter rail fare system
A commuter rail fare system is a structured method for calculating, collecting, and validating payments for passengers traveling on regional rail services, typically based on zones, distance, or time of travel.
-
D.
contactless smart card fare system
A contactless smart card fare system is an electronic payment and access control solution for public transportation that uses proximity cards or devices to automatically deduct fares and manage rider accounts when tapped on compatible readers.
-
E.
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.
- 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3:09 p.m.