Triple
T20894077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lynnwood Link Extension stations |
E514484
|
entity |
| Predicate | corridor |
P5520
|
FINISHED |
| Object | North Seattle–Lynnwood 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: North Seattle–Lynnwood corridor | Statement: [Lynnwood Link Extension stations, corridor, North Seattle–Lynnwood corridor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: North Seattle–Lynnwood corridor Context triple: [Lynnwood Link Extension stations, corridor, North Seattle–Lynnwood corridor]
-
A.
Seattle–Everett corridor
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.
-
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.
Seattle–Bainbridge Island route
The Seattle–Bainbridge Island route is a major Washington State Ferries crossing linking downtown Seattle with Bainbridge Island across Puget Sound.
-
D.
Redmond Central Connector
Redmond Central Connector is an urban trail and linear park in Redmond, Washington, built along a former rail corridor to link regional bike and pedestrian routes with the city’s downtown and public spaces.
-
E.
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.
- 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: North Seattle–Lynnwood corridor Target entity description: The North Seattle–Lynnwood corridor is a major light rail transit corridor in the Seattle metropolitan area connecting neighborhoods in north Seattle with the city of Lynnwood.
-
A.
Seattle–Everett corridor
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.
-
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.
Seattle–Bainbridge Island route
The Seattle–Bainbridge Island route is a major Washington State Ferries crossing linking downtown Seattle with Bainbridge Island across Puget Sound.
-
D.
Redmond Central Connector
Redmond Central Connector is an urban trail and linear park in Redmond, Washington, built along a former rail corridor to link regional bike and pedestrian routes with the city’s downtown and public spaces.
-
E.
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.
- 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_69e0b4f7ebe48190952a85547a0f31a1 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6d06129788190b88ab807af4641c1 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 12:46 p.m.