Triple

T2851858
Position Surface form Disambiguated ID Type / Status
Subject LA Metro A Line E63109 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: [LA Metro A Line, fareSystem, TAP card]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: TAP card
Context triple: [LA Metro A Line, 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. 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. 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.
  • 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_69ab4c407c408190857d25e027155ce9 completed March 6, 2026, 9:50 p.m.
NER Named-entity recognition batch_69abdf5ca2648190bd32c6ec4b0dd3b6 completed March 7, 2026, 8:18 a.m.
NED1 Entity disambiguation (via context triple) batch_69afe8e4e0b881908de5c4927609725e completed March 10, 2026, 9:48 a.m.
Created at: March 6, 2026, 10:02 p.m.