Triple

T3782505
Position Surface form Disambiguated ID Type / Status
Subject STM bus network E85451 entity
Predicate usesTicketMedium P9955 FINISHED
Object OPUS card E85452 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: OPUS card | Statement: [STM bus network, usesTicketMedium, OPUS card]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: OPUS card
Context triple: [STM bus network, usesTicketMedium, 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. 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_69aed937fa8881908208ef3801060826 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aee3db11108190aa81ee8ed22709fe completed March 9, 2026, 3:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4f04353a881908e612a10572eb8c5 completed March 14, 2026, 5:21 a.m.
Created at: March 9, 2026, 3:13 p.m.