Triple

T16982062
Position Surface form Disambiguated ID Type / Status
Subject MARTA Breeze fare system E411968 entity
Predicate supportsDevice P5090 FINISHED
Object Breeze Card E89822 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: Breeze Card | Statement: [MARTA Breeze fare system, supportsDevice, Breeze Card]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Breeze Card
Context triple: [MARTA Breeze fare system, supportsDevice, Breeze Card]
  • A. Breeze Card chosen
    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.
  • 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. SmartRider card
    The SmartRider card is a reusable contactless smartcard used for electronic ticketing on Transperth public transport services in Western Australia.
  • 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. 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.
  • 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_69d886ca8f348190812768ea8d5055ce completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d18830ac8190a20c89a87379ae94 completed April 18, 2026, 6:46 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00dc0d437c81908f003a10b798998a completed May 10, 2026, 7:27 p.m.
Created at: April 10, 2026, 5:32 a.m.