Triple
T6863911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myki |
E158348
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | contactless smartcard ticketing system |
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 ticketing system Context triple: [Myki, instanceOf, contactless smartcard ticketing system]
-
A.
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.
-
B.
public transport ticketing system
A public transport ticketing system manages the purchase, validation, and tracking of fares and passes for passengers across various transit services.
-
C.
public transit fare payment system
A public transit fare payment system manages the calculation, collection, validation, and tracking of passenger payments across various transit services and media (e.g., cards, mobile apps, tickets) to authorize and record travel.
-
D.
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.
-
E.
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.
- 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_69c68830cdbc8190a8301c7a9d9f651a |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:21 p.m.