Triple
T25497156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baseline Street (Hillsboro) |
E639007
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | street in Hillsboro, Oregon |
C50269
|
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 Hillsboro, Oregon Context triple: [Baseline Street (Hillsboro), instanceOf, street in Hillsboro, Oregon]
-
A.
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.
-
B.
street in Las Vegas Valley
A street in the Las Vegas Valley is a public roadway within the metropolitan area surrounding Las Vegas, Nevada, that facilitates local and regional vehicular and pedestrian traffic among residential, commercial, and entertainment destinations.
-
C.
street in Houston
A street in Houston is a public roadway within the city’s grid that facilitates vehicular and pedestrian movement while connecting residential, commercial, and industrial areas across Houston’s diverse neighborhoods.
-
D.
street in Enterprise, Nevada
A street in Enterprise, Nevada is a public roadway within this unincorporated Las Vegas Valley community that provides access to residential, commercial, and recreational areas while connecting local traffic to the broader regional road network.
-
E.
road in Honolulu
A road in Honolulu is a paved transportation route within the city’s limits that supports vehicular, bicycle, and pedestrian travel while connecting local destinations and integrating with the island’s broader traffic and infrastructure network.
- 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_69e75dbbd2a88190b70e1e645de14b9a |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 2:41 p.m.