Triple
T11412275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old York Road (historic route) |
E270400
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial-era transportation route |
C703
|
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: colonial-era transportation route Context triple: [Old York Road (historic route), instanceOf, colonial-era transportation route]
-
A.
ancient trade route
An ancient trade route is a historically established pathway or network used for the long-distance exchange of goods, ideas, cultures, and technologies between regions and civilizations.
-
B.
historic portage route
A historic portage route is a traditional overland path used to carry watercraft and goods between navigable waterways, often significant for its cultural, economic, and transportation history.
-
C.
riverine trade route
A riverine trade route is a navigable waterway along a river system used for the transport and exchange of goods, people, and cultural influences between settlements.
-
D.
historic road
chosen
A historic road is a transportation route of significant age and cultural, economic, or political importance, preserved or recognized for its role in shaping historical events, trade, or settlement patterns.
-
E.
Indigenous travel corridor
An Indigenous travel corridor is a traditional route or network of pathways used by Indigenous peoples for movement, trade, cultural exchange, and connection across their ancestral lands.
- 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:34 p.m.