Triple

T22318805
Position Surface form Disambiguated ID Type / Status
Subject Zone 3 (WMATA fare structure) E551724 entity
Predicate partOf P40 FINISHED
Object Washington Metro distance-based fare system NE NERFINISHED

How this triple was built (3 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: Washington Metro distance-based fare system | Statement: [Zone 3 (WMATA fare structure), partOf, Washington Metro distance-based fare system]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Washington Metro distance-based fare system
Context triple: [Zone 3 (WMATA fare structure), partOf, Washington Metro distance-based fare system]
  • A. flat fare (Washington Metro)
    The flat fare in the Washington Metro is a simplified pricing system where riders pay a uniform fare regardless of travel distance or zones.
  • B. MARC fare system
    The MARC fare system is the ticketing and pricing structure used by Maryland's MARC commuter rail service for travel across its network.
  • C. NFTA Metro system
    The NFTA Metro system is the public transit network serving the Buffalo–Niagara region of New York, providing bus and light rail services operated by the Niagara Frontier Transportation Authority.
  • D. MTA New York City Subway fare system
    The MTA New York City Subway fare system is the payment and ticketing framework that governs how riders pay to use New York City’s subway network, including methods like MetroCard and OMNY.
  • E. SL fare system
    The SL fare system is Stockholm’s integrated public transport ticketing scheme that allows passengers to use a unified range of tickets and travel cards across buses, metro, commuter trains, and other regional services.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Washington Metro distance-based fare system
Target entity description: The Washington Metro distance-based fare system is a pricing structure that charges riders according to how far and when they travel on the Metrorail network, using defined zones and peak/off-peak rates.
  • A. flat fare (Washington Metro)
    The flat fare in the Washington Metro is a simplified pricing system where riders pay a uniform fare regardless of travel distance or zones.
  • B. MARC fare system
    The MARC fare system is the ticketing and pricing structure used by Maryland's MARC commuter rail service for travel across its network.
  • C. NFTA Metro system
    The NFTA Metro system is the public transit network serving the Buffalo–Niagara region of New York, providing bus and light rail services operated by the Niagara Frontier Transportation Authority.
  • D. MTA New York City Subway fare system
    The MTA New York City Subway fare system is the payment and ticketing framework that governs how riders pay to use New York City’s subway network, including methods like MetroCard and OMNY.
  • E. SL fare system
    The SL fare system is Stockholm’s integrated public transport ticketing scheme that allows passengers to use a unified range of tickets and travel cards across buses, metro, commuter trains, and other regional services.
  • F. None of above. chosen

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_69e11e4776588190abb21e5cea79973f completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15762fac08190a6a514baffbbbca1 completed April 29, 2026, 12:57 a.m.
Created at: April 16, 2026, 8:42 p.m.