Triple
T568086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hop Fastpass |
E13600
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transit smart card |
C1449
|
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 transit smart card Context triple: [Hop Fastpass, instanceOf, public transit smart card]
-
A.
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.
-
B.
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.
-
C.
public transit fare card
chosen
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.
-
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.
fare card
A fare card is a reusable, often electronic, payment token used to access and pay for rides on public transportation systems.
- 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_69a4933fa4d88190a7949cc83c08c5c1 |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:33 p.m.