Triple
T27407559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King George Boulevard |
E692048
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | street in Surrey, British Columbia |
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 Surrey, British Columbia Context triple: [King George Boulevard, instanceOf, street in Surrey, British Columbia]
-
A.
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.
-
B.
street in Hillsboro, Oregon
A street in Hillsboro, Oregon is a public roadway within the city’s limits that provides access to local residences, businesses, and community facilities while connecting to the broader transportation network of the region.
-
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 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.
-
E.
former street in London
A former street in London is a once-recognized urban thoroughfare within the city that has since been removed, renamed, or absorbed into other developments, leaving it absent from the current street 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_69ef5205fc808190ad3efc5525b8e6d6 |
completed | April 27, 2026, 12:09 p.m. |
Created at: April 27, 2026, 12:31 p.m.