Triple
T2959123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MiWay |
E80002
|
entity |
| Predicate | fareSystem |
P395
|
FINISHED |
| Object | PRESTO card |
E31472
|
NE FINISHED |
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: PRESTO card | Statement: [MiWay, fareSystem, PRESTO card]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PRESTO card Context triple: [MiWay, fareSystem, PRESTO card]
-
A.
Presto card
chosen
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.
-
B.
TAP card
The TAP card is a reusable contactless smart card used to pay fares across public transit systems in the Los Angeles County region.
-
C.
Opal card
The Opal card is a reusable, contactless smartcard used to pay for public transport across much of New South Wales, Australia.
-
D.
ORCA card
The ORCA card is a reusable, contactless smart card used to pay fares across multiple public transit systems in the Puget Sound region of Washington State.
-
E.
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.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69ad8b1341848190bd19dbf46892887d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad992c4c7c819084b5bef299255181 |
completed | March 8, 2026, 3:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b0fc8df3f481908ba71ab72e68938e |
completed | March 11, 2026, 5:24 a.m. |
Created at: March 8, 2026, 2:57 p.m.