Triple
T11449677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Integrated Public Transport Card of Mexico City |
E271360
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rechargeable smart 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: rechargeable smart card Context triple: [Integrated Public Transport Card of Mexico City, instanceOf, rechargeable smart 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.
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.
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.
-
D.
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.
-
E.
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.
- 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_69d6aadff8888190a13f253f0d460874 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:35 p.m.