Triple
T28556425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 82 Business (Yakima, Washington) |
E723019
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | highway in Washington |
C37610
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: highway in Washington Context triple: [Interstate 82 Business (Yakima, Washington), instanceOf, highway in Washington]
-
A.
road in Washington State
A road in Washington State is a constructed transportation route within the state's boundaries that facilitates vehicular travel between locations, adhering to state and local regulations and infrastructure standards.
-
B.
street in Washington State
A street in Washington State is a public roadway within the state's boundaries that facilitates vehicular and pedestrian travel, often connecting residential, commercial, and natural areas under local or state jurisdiction.
-
C.
highway
A highway is a major public road designed for high-speed, long-distance vehicular travel, typically featuring multiple lanes, limited access points, and safety infrastructure.
-
D.
segment of Washington State Route 99
A segment of Washington State Route 99 represents a continuous portion of the state highway between two defined endpoints, characterized by its specific location, roadway features, and role in regional transportation.
-
E.
highway route
chosen
A highway route is a designated path along interconnected roads or highways, identified by a specific number or name, that guides long-distance vehicular travel between regions or destinations.
- F. None of above.
Provenance (1 batch)
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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 3:46 a.m.