Triple
T4062697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ScotRail smartcard |
E86251
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | contactless 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: contactless smartcard Context triple: [ScotRail smartcard, instanceOf, contactless smartcard]
-
A.
contactless smart card standard
A contactless smart card standard defines the technical specifications and communication protocols that enable secure, wireless data exchange between smart cards and readers without physical contact.
-
B.
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.
-
C.
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.
-
D.
contactless access system
A contactless access system is a security solution that grants or denies entry to users through non-physical interaction methods such as RFID cards, mobile credentials, or biometrics, enhancing convenience and hygiene while maintaining controlled access.
-
E.
magnetic stripe card
A magnetic stripe card is a plastic card that stores data in a magnetizable stripe on its surface, enabling electronic reading for identification, access control, or financial transactions.
- 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_69aed93c69208190a4efac0efe3cd69b |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:38 p.m.