Triple

T18626668
Position Surface form Disambiguated ID Type / Status
Subject Shenzhen Tong card E455301 entity
Predicate similarTo P4460 FINISHED
Object Octopus card NE NERFINISHED

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: Octopus card | Statement: [Shenzhen Tong card, similarTo, Octopus card]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Octopus card
Context triple: [Shenzhen Tong card, similarTo, Octopus card]
  • A. Octopus card chosen
    The Octopus card is a rechargeable contactless smart card widely used in Hong Kong for public transport fares and everyday electronic payments.
  • B. Oyster card
    The Oyster card is a rechargeable smartcard used for convenient, cashless payment on public transport services across London.
  • 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. Opal card
    The Opal card is a reusable, contactless smartcard used to pay for public transport across much of New South Wales, Australia.
  • E. 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.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8d38cc7948190a55ea64e5638994e completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e54f0581f0819083c1aba9fb85f6a7 completed April 19, 2026, 9:54 p.m.
Created at: April 10, 2026, 11:46 a.m.