Triple

T17406533
Position Surface form Disambiguated ID Type / Status
Subject Sounder E423229 entity
Predicate hasRoute P4374 FINISHED
Object Seattle–Everett corridor 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: Seattle–Everett corridor | Statement: [Sounder, hasRoute, Seattle–Everett corridor]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Seattle–Everett corridor
Context triple: [Sounder, hasRoute, Seattle–Everett corridor]
  • A. Seattle–Tacoma urban corridor
    The Seattle–Tacoma urban corridor is a densely developed metropolitan region in western Washington State that encompasses and connects the major cities of Seattle and Tacoma along the Puget Sound.
  • B. Tacoma–Bremerton travel corridor
    The Tacoma–Bremerton travel corridor is a key transportation route in Washington State linking the city of Tacoma with Bremerton across Puget Sound via highways and ferry connections.
  • C. Eugene–Portland–Seattle–Vancouver corridor
    The Eugene–Portland–Seattle–Vancouver corridor is a major north–south passenger rail and transportation route in the Pacific Northwest, linking key cities in Oregon, Washington, and British Columbia.
  • D. Vancouver–Seattle corridor
    The Vancouver–Seattle corridor is a major bi-national urban and transportation axis linking metropolitan regions in southwestern British Columbia and northwestern Washington State.
  • E. Empire Corridor
    The Empire Corridor is a major passenger rail route in New York State, running from New York City through the Hudson Valley and up to cities such as Albany and Buffalo.
  • 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: Seattle–Everett corridor
Target entity description: The Seattle–Everett corridor is a heavily traveled stretch of the Puget Sound region in Washington State connecting the cities of Seattle and Everett, served by commuter rail and major highways.
  • A. Seattle–Tacoma urban corridor
    The Seattle–Tacoma urban corridor is a densely developed metropolitan region in western Washington State that encompasses and connects the major cities of Seattle and Tacoma along the Puget Sound.
  • B. Tacoma–Bremerton travel corridor
    The Tacoma–Bremerton travel corridor is a key transportation route in Washington State linking the city of Tacoma with Bremerton across Puget Sound via highways and ferry connections.
  • C. Eugene–Portland–Seattle–Vancouver corridor
    The Eugene–Portland–Seattle–Vancouver corridor is a major north–south passenger rail and transportation route in the Pacific Northwest, linking key cities in Oregon, Washington, and British Columbia.
  • D. Vancouver–Seattle corridor
    The Vancouver–Seattle corridor is a major bi-national urban and transportation axis linking metropolitan regions in southwestern British Columbia and northwestern Washington State.
  • E. Empire Corridor
    The Empire Corridor is a major passenger rail route in New York State, running from New York City through the Hudson Valley and up to cities such as Albany and Buffalo.
  • 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_69d889d7d27c819088486ce3f0627fa1 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e43b081ae08190b144e333a3a74b02 completed April 19, 2026, 2:16 a.m.
Created at: April 10, 2026, 5:45 a.m.