Triple
T23021602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Road |
E573179
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | neighborhood in Milwaukie, Oregon |
C27
|
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: neighborhood in Milwaukie, Oregon Context triple: [Lake Road, instanceOf, neighborhood in Milwaukie, Oregon]
-
A.
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.
-
B.
district of Portland, Oregon
A district of Portland, Oregon is a defined geographic area within the city that groups together neighborhoods sharing common administrative, cultural, or commercial characteristics.
-
C.
neighborhood
chosen
A neighborhood is a geographically localized community within a larger city or town, characterized by shared residential spaces, social interactions, and common amenities.
-
D.
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.
-
E.
neighborhood of Oslo
A neighborhood of Oslo is a distinct, localized area within the city characterized by its own residential patterns, amenities, cultural features, and community identity while remaining integrated into the broader urban structure of Oslo.
- 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_69e245b821008190b0e09cb02092aae1 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:52 p.m.