Triple
T26500087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White River Road |
E669394
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road in Washington State |
C51657
|
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: road in Washington State Context triple: [White River Road, instanceOf, road in Washington State]
-
A.
road in West Virginia
A road in West Virginia is a transportation route, ranging from winding rural byways to major highways, that traverses the state's mountainous terrain to connect its towns, cities, and natural landmarks.
-
B.
road in Portland, Oregon
A road in Portland, Oregon is a public vehicular and pedestrian thoroughfare within the city’s transportation network, defined by its physical layout, traffic regulations, and integration with local infrastructure and land use.
-
C.
road in Michigan
A road in Michigan is a designated vehicular travel way within the state’s boundaries, ranging from local streets to major highways, that facilitates transportation, commerce, and connectivity among Michigan’s communities and regions.
-
D.
road in Minnesota
A road in Minnesota is a constructed transportation route within the state that facilitates vehicular travel across its urban, suburban, and rural landscapes, often designed to withstand harsh seasonal weather conditions.
-
E.
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.
- F. None of above. chosen
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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
Created at: April 27, 2026, 1:12 a.m.