Triple
T7215267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maple GO Station |
E149514
|
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: [Maple GO Station, fareSystem, PRESTO card]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PRESTO card Context triple: [Maple GO Station, 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.
SmartRider card
The SmartRider card is a reusable contactless smartcard used for electronic ticketing on Transperth public transport services in Western Australia.
-
E.
Metro TAP card
The Metro TAP card is a reusable, reloadable smart fare card used for contactless payment across the Los Angeles County public transit system.
- 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_69c687eca814819095abb52316b1af80 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e98ebe1c81909891b4a1c2c3a4aa |
completed | March 27, 2026, 8:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7bfd82c488190bfa85ffdd7f385ef |
completed | March 28, 2026, 11:47 a.m. |
Created at: March 27, 2026, 2:53 p.m.