Triple

T4435465
Position Surface form Disambiguated ID Type / Status
Subject Bessarion E95637 entity
Predicate ticketingSystem P3383 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: [Bessarion, ticketingSystem, Presto card]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Presto card
Context triple: [Bessarion, ticketingSystem, 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. Pronto card
    The Pronto card is a reloadable smart fare card used for paying public transit fares across the San Diego Metropolitan Transit System and related services.
  • C. Clipper card
    The Clipper card is a reloadable contactless smart card used to pay fares across multiple public transit systems in the San Francisco Bay Area.
  • D. Breeze Card
    The Breeze Card is a reusable smart fare card used for paying transit fares across the Metropolitan Atlanta Rapid Transit Authority (MARTA) system in Atlanta, Georgia.
  • E. 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.
  • 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_69b3453ea2b48190a26f154b3b8fece5 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b35589f8608190b0820d36beaacf44 completed March 13, 2026, 12:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69b61377180c8190898300fe0cd77433 completed March 15, 2026, 2:03 a.m.
Created at: March 12, 2026, 11:31 p.m.