Triple
T19423661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SwissPass |
E485924
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transport smartcard |
C4037
|
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 transport smartcard Context triple: [SwissPass, instanceOf, public transport smartcard]
-
A.
smartcard
A smartcard is a portable, tamper-resistant card containing an embedded microchip that securely stores and processes data for identification, authentication, and transaction purposes.
-
B.
contactless smart card fare system
chosen
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.
-
C.
contact-type smart card
A contact-type smart card is a plastic card with an embedded integrated circuit chip that must physically connect to a reader via metallic contacts to securely store, process, and exchange data for applications like payments and identification.
-
D.
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.
-
E.
public transportation payment compatibility
The public transportation payment compatibility class represents the ability of a transit system to accept, interoperate with, and correctly process various payment methods and fare media across different services and platforms.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:37 p.m.