Triple
T1338394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OV-chipkaart |
E28408
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fare collection system |
C4038
|
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 collection system Context triple: [OV-chipkaart, instanceOf, fare collection system]
-
A.
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.
-
B.
public transit fare payment system
chosen
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.
fare payment card
A fare payment card is a reusable, often contactless card or digital token used to store and deduct monetary value or passes for accessing public transportation services.
-
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.
fare card
A fare card is a reusable, often electronic, payment token used to access and pay for rides on public transportation systems.
- 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_69a49854eb3481908c7d56b2e449a290 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:56 p.m.