Triple
T6151532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto Carrying-Place route |
E137214
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indigenous travel corridor |
C20021
|
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: Indigenous travel corridor Context triple: [Toronto Carrying-Place route, instanceOf, Indigenous travel corridor]
-
A.
United States National Historic Trail
A United States National Historic Trail is a federally designated long-distance route that commemorates and protects significant historical travel paths, events, and landscapes across the nation.
-
B.
state scenic corridor
A state scenic corridor is a designated roadway or linear area recognized and protected by a state for its outstanding natural, cultural, or visual qualities, often with special regulations to preserve its scenic character.
-
C.
ecological corridor
An ecological corridor is a natural or restored habitat pathway that connects separate wildlife populations, enabling species movement, gene flow, and ecosystem resilience across fragmented landscapes.
-
D.
transport corridor
A transport corridor is a designated route or geographic band that concentrates and connects major transportation infrastructure—such as roads, railways, ports, and logistics hubs—to facilitate efficient movement of people and goods between key locations.
-
E.
scenic byway
A scenic byway is a designated roadway recognized for its exceptional natural, cultural, historic, or recreational qualities, offering travelers a visually and experientially rich driving route.
- 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_69c008a45d008190832a9e19f5d63406 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:16 p.m.