Triple
T31073884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lauzon Parkway |
E791897
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | street in Windsor, Ontario |
C54611
|
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 Windsor, Ontario Context triple: [Lauzon Parkway, instanceOf, street in Windsor, Ontario]
-
A.
street in Ontario
chosen
A street in Ontario is a public roadway within the province’s municipalities that facilitates vehicular and pedestrian travel, connects properties and local destinations, and is governed by provincial and municipal traffic, zoning, and safety regulations.
-
B.
street in Surrey, British Columbia
A street in Surrey, British Columbia is a public roadway within the city’s urban or suburban areas that facilitates vehicular and pedestrian movement while connecting residential, commercial, and community spaces.
-
C.
road in London, Ontario
A road in London, Ontario is a designated public thoroughfare within the city’s transportation network that facilitates vehicular, cyclist, and pedestrian movement between local destinations and connecting routes.
-
D.
street in Richmond, British Columbia
A street in Richmond, British Columbia is a public roadway within the city’s flat, coastal urban landscape that supports local and through traffic, connects residential, commercial, and industrial areas, and often incorporates features for pedestrians, cyclists, and transit.
-
E.
road in Toronto
A road in Toronto is a public thoroughfare within the city’s transportation network that facilitates vehicular, cycling, and pedestrian movement while connecting residential, commercial, and institutional areas.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:01 p.m.