Triple

T4974933
Position Surface form Disambiguated ID Type / Status
Subject Thames Clippers river bus services E111740 entity
Predicate accepts P273 FINISHED
Object Oyster card E60075 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: Oyster card | Statement: [Thames Clippers river bus services, accepts, Oyster card]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oyster card
Context triple: [Thames Clippers river bus services, accepts, Oyster card]
  • A. Oyster card chosen
    The Oyster card is a rechargeable smartcard used for convenient, cashless payment on public transport services across London.
  • B. 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.
  • C. 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.
  • D. Opal card
    The Opal card is a reusable, contactless smartcard used to pay for public transport across much of New South Wales, Australia.
  • E. Travelcard Zone 1
    Travelcard Zone 1 is the central London fare zone covering the city’s core Underground and rail stations, including many major commercial, tourist, and transport hubs.
  • 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_69bd441a0eb481908050fa4273b19eae completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd722e77208190833dc760a57428d5 completed March 20, 2026, 4:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69be8a01e548819087e3a6ae2cd581b9 completed March 21, 2026, 12:07 p.m.
Created at: March 20, 2026, 1:33 p.m.