Triple
T920250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon Trail |
E19866
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic overland migration route |
C1081
|
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: historic overland migration route Context triple: [Oregon Trail, instanceOf, historic overland migration route]
-
A.
historic road
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.
-
B.
historic transportation system
chosen
A historic transportation system is an organized network of vehicles, routes, and infrastructure from a past era that once facilitated the movement of people or goods and is now preserved, studied, or remembered for its cultural, technological, or historical significance.
-
C.
historic walking trail
A historic walking trail is a designated pedestrian route that guides visitors through significant historical sites, landmarks, and narratives within a specific area.
-
D.
transcontinental automobile route
A transcontinental automobile route is a long-distance roadway or network of connected highways that enables continuous vehicular travel across an entire continent from one coast or border to another.
-
E.
long-distance hiking trail
A long-distance hiking trail is an extended, often multi-day walking route designed for recreational trekking through diverse natural landscapes, typically marked and maintained for continuous foot travel.
- 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_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:40 p.m.