Triple
T3746121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC 14443 |
E81215
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | contactless smart card standard |
C14044
|
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 smart card standard Context triple: [ISO/IEC 14443, instanceOf, contactless smart card standard]
-
A.
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.
-
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.
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.
-
D.
stored-value card
A stored-value card is a payment card preloaded with a specific monetary amount that can be used to make purchases or access services until its balance is depleted or reloaded.
-
E.
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.
- F. None of above. chosen
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_69ad8b19b7b08190a6188804e99c53e9 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:35 p.m.