Triple
T17721621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adult Opal card |
E442350
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | reloadable contactless payment card |
C1688
|
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: reloadable contactless payment card Context triple: [Adult Opal card, instanceOf, reloadable contactless payment card]
-
A.
disposable smart card
A disposable smart card is a low-cost, single-use or limited-use card embedded with a microchip that securely stores and processes data for temporary transactions or access control before being discarded.
-
B.
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.
-
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.
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.
stored-value card
chosen
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.
- 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:07 a.m.