Triple
T25967676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baseline Road |
E645717
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | street in Ottawa |
C46157
|
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 Ottawa Context triple: [Baseline Road, instanceOf, street in Ottawa]
-
A.
road in Ottawa
chosen
A road in Ottawa is a public thoroughfare within the city’s transportation network that facilitates vehicular, cycling, and pedestrian movement while connecting residential, commercial, and institutional areas.
-
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.
road in Canada
A road in Canada is a constructed transportation route, ranging from local streets to major highways, designed to support vehicular and sometimes pedestrian traffic across the country's diverse and often harsh climatic and geographic conditions.
-
D.
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.
-
E.
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.
- 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_69e77e8768648190b27bb578f14bcb88 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 22, 2026, 8:50 a.m.