Triple

T649249
Position Surface form Disambiguated ID Type / Status
Subject Metro Bike Share E11308 entity
Predicate usesPaymentMethod P5428 FINISHED
Object TAP card E11309 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: TAP card | Statement: [Metro Bike Share, usesPaymentMethod, TAP card]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: TAP card
Context triple: [Metro Bike Share, usesPaymentMethod, TAP card]
  • A. TAP card chosen
    The TAP card is a reusable contactless smart card used to pay fares across public transit systems in the Los Angeles County region.
  • 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. ORCA card
    The ORCA card is a reusable, contactless smart card used to pay fares across multiple public transit systems in the Puget Sound region of Washington State.
  • D. 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.
  • E. Oyster card
    The Oyster card is a rechargeable smartcard used for convenient, cashless payment on public transport services across London.
  • 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_69a493266a2881909daf4c40f719dee8 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a49f31e70c81909a2ac1d939f7ec07 completed March 1, 2026, 8:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69a58a716de88190854e13fb5143b9b3 completed March 2, 2026, 1:02 p.m.
Created at: March 1, 2026, 7:36 p.m.