Triple

T13504692
Position Surface form Disambiguated ID Type / Status
Subject Pershing Square E320983 entity
Predicate fareSystem P395 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: [Pershing Square, fareSystem, TAP Card]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: TAP Card
Context triple: [Pershing Square, fareSystem, 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. Opal card
    The Opal card is a reusable, contactless smartcard used to pay for public transport across much of New South Wales, Australia.
  • C. 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.
  • D. STIF card
    The STIF card was a contactless smart card used for public transportation in the Île-de-France region before being rebranded as the Navigo pass.
  • E. 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.
  • 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_69d807629d6c8190998f1b9bb12d2ed0 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbaf810e248190a060481004503f96 completed April 12, 2026, 2:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69f7548bc188819090773db66b0103a1 completed May 3, 2026, 1:58 p.m.
Created at: April 9, 2026, 9:43 p.m.