Triple

T4708861
Position Surface form Disambiguated ID Type / Status
Subject Auckland Transport E104458 entity
Predicate usesTicketingSystem P1740 FINISHED
Object AT HOP card
The AT HOP card is a reusable, contactless smart card used for paying fares on public transport services across Auckland, New Zealand.
 E464219 NE FINISHED

How this triple was built (4 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: AT HOP card | Statement: [Auckland Transport, usesTicketingSystem, AT HOP card]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: AT HOP card
Context triple: [Auckland Transport, usesTicketingSystem, AT HOP card]
  • A. 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.
  • 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. TAP card
    The TAP card is a reusable contactless smart card used to pay fares across public transit systems in the Los Angeles County region.
  • D. Clipper card
    The Clipper card is a reloadable contactless smart card used to pay fares across multiple public transit systems in the San Francisco Bay Area.
  • E. METRO Q Card
    The METRO Q Card is a reusable, reloadable smart fare card used to pay for rides on Houston’s METRO public transit system.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: AT HOP card
Triple: [Auckland Transport, usesTicketingSystem, AT HOP card]
Generated description
The AT HOP card is a reusable, contactless smart card used for paying fares on public transport services across Auckland, New Zealand.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: AT HOP card
Target entity description: The AT HOP card is a reusable, contactless smart card used for paying fares on public transport services across Auckland, New Zealand.
  • A. 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.
  • 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. TAP card
    The TAP card is a reusable contactless smart card used to pay fares across public transit systems in the Los Angeles County region.
  • D. Clipper card
    The Clipper card is a reloadable contactless smart card used to pay fares across multiple public transit systems in the San Francisco Bay Area.
  • E. METRO Q Card
    The METRO Q Card is a reusable, reloadable smart fare card used to pay for rides on Houston’s METRO public transit system.
  • F. None of above. chosen

Provenance (5 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_69bd43eac3c08190af7e4020c6c3704c completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd63ed2ed081908cd52570ba085806 completed March 20, 2026, 3:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69be10721b88819093be46bc5cae17c0 completed March 21, 2026, 3:28 a.m.
NEDg Description generation batch_69be1452eba88190bf982ab0f464e96f completed March 21, 2026, 3:45 a.m.
NED2 Entity disambiguation (via description) batch_69be14ca370481909c5e144e63ceb495 completed March 21, 2026, 3:47 a.m.
Created at: March 20, 2026, 1:17 p.m.