Triple

T21855576
Position Surface form Disambiguated ID Type / Status
Subject Viva Yellow E539615 entity
Predicate usesTicketingSystem P1740 FINISHED
Object PRESTO 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: PRESTO card | Statement: [Viva Yellow, usesTicketingSystem, PRESTO card]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: PRESTO card
Context triple: [Viva Yellow, usesTicketingSystem, 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. STIF card
    The STIF card was a contactless smart card used for public transportation in the Île-de-France region before being rebranded as the Navigo pass.
  • C. 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.
  • 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. Octopus card
    The Octopus card is a rechargeable contactless smart card widely used in Hong Kong for public transport fares and everyday electronic payments.
  • 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_69e0c47829648190bbe2d1d7033768ec completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f0d635b59c81908810480f3802b847 completed April 28, 2026, 3:45 p.m.
Created at: April 16, 2026, 6:56 p.m.