Triple
T26431354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evergreen Way |
E664517
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | street in Everett, Washington |
C51558
|
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 Everett, Washington Context triple: [Evergreen Way, instanceOf, street in Everett, Washington]
-
A.
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.
-
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.
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.
-
D.
neighborhood of Kirkland, Washington
A neighborhood of Kirkland, Washington is a distinct residential and mixed-use area within the city characterized by its local amenities, community identity, and geographic boundaries along Lake Washington’s eastern shore.
-
E.
region of Seattle
A region of Seattle represents a specific geographic area within the city, defined by boundaries and associated with particular neighborhoods, landmarks, and administrative or cultural characteristics.
- 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_69ee883ad6a4819088f918e76122d690 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 26, 2026, 11:49 p.m.