Triple

T16488763
Position Surface form Disambiguated ID Type / Status
Subject Miami Metrorail stations E400516 entity
Predicate fareSystem P395 FINISHED
Object EASY Ticket E311297 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: EASY Ticket | Statement: [Miami Metrorail stations, fareSystem, EASY Ticket]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: EASY Ticket
Context triple: [Miami Metrorail stations, fareSystem, EASY Ticket]
  • A. EASY Ticket chosen
    EASY Ticket is a rechargeable smart fare card used by Miami-Dade Metrorail and related transit services for convenient electronic payment of rides.
  • B. Breeze Ticket
    Breeze Ticket is MARTA’s reloadable smart fare card used for paying bus and rail fares in the Atlanta public transit system.
  • C. CharlieTicket
    CharlieTicket is a reusable paper smart card used for paying fares on Boston’s MBTA public transit system.
  • D. EASY Card
    The EASY Card is a contactless smart card used as a stored-value payment method for public transit services in the Miami-Dade area.
  • E. Weekend Ticket
    Weekend Ticket is a discounted Belgian train fare offered by NMBS/SNCB that allows passengers to make return journeys at reduced prices over the weekend.
  • 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_69d883813098819084f5409539723b59 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e32e2e3bf88190ba6eac85a79e5ac8 completed April 18, 2026, 7:09 a.m.
NED1 Entity disambiguation (via context triple) batch_6a00582472388190a3c338ab636da9c6 completed May 10, 2026, 10:04 a.m.
Created at: April 10, 2026, 5:13 a.m.