Triple
T17721410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opal network |
E442345
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transport smartcard 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: public transport smartcard system Context triple: [Opal network, instanceOf, public transport smartcard 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 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.
-
C.
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.
-
D.
public transport information system
A public transport information system is a software platform that collects, processes, and disseminates real-time and scheduled data about public transit services to passengers, operators, and other stakeholders.
-
E.
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.
- 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.