Triple
T21537506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viau |
E531385
|
entity |
| Predicate | hasFareSystem |
P395
|
FINISHED |
| Object | OPUS card |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: OPUS card | Statement: [Viau, hasFareSystem, OPUS card]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OPUS card Context triple: [Viau, hasFareSystem, OPUS card]
-
A.
OPUS card
chosen
The OPUS card is a reusable, contactless smart card used for public transit fare payment across the greater Montreal area and other regions in Quebec.
-
B.
Presto card
The Presto card is a reloadable smart card used for paying public transit fares across the Greater Toronto and Hamilton Area and other regions in Ontario, Canada.
-
C.
Bilhete Único smart card
The Bilhete Único smart card is São Paulo’s integrated public transport fare card, allowing seamless, discounted transfers across the city’s metro, bus, and train networks.
-
D.
Opal card
The Opal card is a reusable, contactless smartcard used to pay for public transport across much of New South Wales, Australia.
-
E.
Metcard
Metcard was Melbourne’s former magnetic stripe ticketing system used for public transport before the introduction of the Myki smartcard.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 batches)
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_69e0c45e5b8881908ac18fc2f493b114 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee9d0fdf448190b47ac7c28904f86b |
completed | April 26, 2026, 11:17 p.m. |
Created at: April 16, 2026, 6:27 p.m.