Triple

T15836404
Position Surface form Disambiguated ID Type / Status
Subject Expo/Western station E383995 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: [Expo/Western station, fareSystem, TAP card]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: TAP card
Context triple: [Expo/Western station, 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. 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.
  • D. 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.
  • E. 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.
  • 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_69d86da34c888190976e06c4019d415a completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e142e1fcd48190bcb884f6c65db847 completed April 16, 2026, 8:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffa13a83448190adcad8bb84622e55 completed May 9, 2026, 9:03 p.m.
Created at: April 10, 2026, 4:49 a.m.