Triple

T11586358
Position Surface form Disambiguated ID Type / Status
Subject Go-To Card E274764 entity
Predicate usedOn P2367 FINISHED
Object METRO light rail E56106 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: METRO light rail | Statement: [Go-To Card, usedOn, METRO light rail]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: METRO light rail
Context triple: [Go-To Card, usedOn, METRO light rail]
  • A. METRO light rail chosen
    METRO light rail is a rapid transit system serving the Minneapolis–Saint Paul metropolitan area with multiple color-designated lines connecting key urban, suburban, and airport destinations.
  • B. METRORail light rail
    METRORail light rail is Houston's urban light rail transit system operated by METRO, connecting key destinations throughout the city’s central area.
  • C. MAX Light Rail
    MAX Light Rail is the metropolitan light rail transit system serving the Portland, Oregon, metropolitan area.
  • D. Metro Rail
    Metro Rail is the urban rapid transit rail system serving Los Angeles County, providing light rail and subway services across the region.
  • E. DART Light Rail
    DART Light Rail is a light rail transit system serving the Dallas–Fort Worth metropolitan area, operated by Dallas Area Rapid Transit.
  • 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_69d6aae6b14c81908dc5a74bad7591f9 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d89462203881908870e991a5b21770 completed April 10, 2026, 6:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69e7143ee0548190b71ddae0ab7c68cb completed April 21, 2026, 6:07 a.m.
Created at: April 8, 2026, 9:38 p.m.