Triple

T16792679
Position Surface form Disambiguated ID Type / Status
Subject 28th Street (BMT Broadway Line) E408150 entity
Predicate fareControlSystem P395 FINISHED
Object MetroCard E3073 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: MetroCard | Statement: [28th Street (BMT Broadway Line), fareControlSystem, MetroCard]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: MetroCard
Context triple: [28th Street (BMT Broadway Line), fareControlSystem, MetroCard]
  • A. MetroCard chosen
    MetroCard is a magnetic stripe payment card formerly used as the primary method for paying fares on New York City’s public transit system, including subways and buses.
  • B. SmarTrip
    SmarTrip is a rechargeable contactless smart card used to pay fares on the Washington, D.C. region’s public transit systems.
  • 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. Octopus card
    The Octopus card is a rechargeable contactless smart card widely used in Hong Kong for public transport fares and everyday electronic payments.
  • 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.
  • 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_69d88393905081908d00a86b99996ac8 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3b2a7817c8190a53d0cfb5ef66a71 completed April 18, 2026, 4:34 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00aafc28c0819084ecd6e5be6adec9 completed May 10, 2026, 3:57 p.m.
Created at: April 10, 2026, 5:22 a.m.