Triple
T26878363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bothell Way NE |
E676817
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | street in Washington State |
C52158
|
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: street in Washington State Context triple: [Bothell Way NE, instanceOf, street in Washington State]
-
A.
street in Everett, Washington
A street in Everett, Washington is a public roadway within the city’s limits that facilitates local and through traffic, provides access to residential, commercial, and industrial properties, and connects neighborhoods to the broader regional transportation network.
-
B.
city in Washington State
A city in Washington State is an incorporated urban municipality within the state’s boundaries that provides local government services, infrastructure, and regulations to its residents and businesses.
-
C.
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.
-
D.
road in Washington, D.C.
A road in Washington, D.C. is a public thoroughfare within the District’s street network, designed for vehicular and pedestrian travel and organized according to the city’s distinctive grid and diagonal avenue system.
-
E.
street in Hillsboro, Oregon
A street in Hillsboro, Oregon is a public roadway within the city’s limits that provides access to local residences, businesses, and community facilities while connecting to the broader transportation network of the region.
- 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 5:37 a.m.