Triple

T8254068
Position Surface form Disambiguated ID Type / Status
Subject TransLink card E193026 entity
Predicate predecessorOf P97 FINISHED
Object Clipper card system E38241 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: Clipper card system | Statement: [TransLink card, predecessorOf, Clipper card system]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Clipper card system
Context triple: [TransLink card, predecessorOf, Clipper card system]
  • A. Clipper card chosen
    The Clipper card is a reloadable contactless smart card used to pay fares across multiple public transit systems in the San Francisco Bay Area.
  • B. Opal card
    The Opal card is a reusable, contactless smartcard used to pay for public transport across much of New South Wales, Australia.
  • C. 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.
  • D. 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.
  • E. SmarTrip
    SmarTrip is a rechargeable contactless smart card used to pay fares on the Washington, D.C. region’s public transit systems.
  • 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_69ca82dfad9c8190b8cd18fb89f50f40 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb78f8eccc8190b43204bf2f8defc1 completed March 31, 2026, 7:34 a.m.
NED1 Entity disambiguation (via context triple) batch_69cd94f9c97881908c6e9f266aba888e completed April 1, 2026, 9:58 p.m.
Created at: March 30, 2026, 5:48 p.m.