Triple
T25588013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myki Pass |
E641439
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Myki product |
C3473
|
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: Myki product Context triple: [Myki Pass, instanceOf, Myki product]
-
A.
transit fare product
A transit fare product is a purchasable medium (such as a ticket, pass, or stored value) that grants a rider the right to access and use public transportation services under specified conditions.
-
B.
fare card
chosen
A fare card is a reusable, often electronic, payment token used to access and pay for rides on public transportation systems.
-
C.
public transportation payment compatibility
The public transportation payment compatibility class represents the ability of a transit system to accept, interoperate with, and correctly process various payment methods and fare media across different services and platforms.
-
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.
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.
- 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 4:17 p.m.