Triple
T23675501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King’s Highway 2 |
E584861
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former Ontario provincial highway |
C45094
|
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: former Ontario provincial highway Context triple: [King’s Highway 2, instanceOf, former Ontario provincial highway]
-
A.
road in New Brunswick
A road in New Brunswick is a designated transportation corridor within the province that facilitates vehicular travel between communities, regions, and key destinations, following provincial standards for construction, maintenance, and signage.
-
B.
road in Nova Scotia
A road in Nova Scotia is a constructed transportation route, ranging from major highways to local streets, that connects communities across the province and supports the movement of people, goods, and services.
-
C.
former national highway of India
A former national highway of India is a roadway that was once part of the country's officially designated national highway network but has since been renumbered, reclassified, or decommissioned from that status.
-
D.
former highway name
chosen
A former highway name is a historical designation once used to identify a specific roadway or route that has since been renumbered, renamed, decommissioned, or otherwise replaced in official records and signage.
-
E.
former state highway designation
A former state highway designation is an official route number or name that was once assigned to a state-maintained roadway but has since been removed, reassigned, or decommissioned from the state highway system.
- 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_69e24901f7c08190909fd727632e823d |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:51 p.m.