Triple
T28757819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Road |
E731719
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | street in Metro Vancouver |
C52781
|
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 Metro Vancouver Context triple: [North Road, instanceOf, street in Metro Vancouver]
-
A.
street in Surrey, British Columbia
chosen
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.
-
B.
street in Montreal
A street in Montreal is a public urban thoroughfare that reflects the city’s blend of historic European-influenced architecture, diverse neighborhoods, bilingual culture, and seasonal climate, supporting vehicular, pedestrian, and often cycling traffic.
-
C.
street in Melbourne
A street in Melbourne is a public urban thoroughfare within the city’s grid or suburban layout, lined with a mix of residential, commercial, and cultural buildings, and shaped by the city’s distinctive tram network, laneways, and diverse neighborhoods.
-
D.
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.
-
E.
street in Washington State
A street in Washington State is a public roadway within the state's boundaries that facilitates vehicular and pedestrian travel, often connecting residential, commercial, and natural areas under local or state jurisdiction.
- 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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 6:10 a.m.