Triple
T33883641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lander Cutoff of the Oregon Trail |
E868564
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic emigrant trail route |
C7367
|
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 emigrant trail route Context triple: [Lander Cutoff of the Oregon Trail, instanceOf, historic emigrant trail route]
-
A.
emigrant trail
chosen
An emigrant trail is a historically established overland route used by groups of people leaving their homeland to settle in a new region or country.
-
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.
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.
-
D.
historic passageway
A historic passageway is an architectural corridor, alley, or tunnel that has been preserved or recognized for its cultural, historical, or architectural significance as a route connecting different spaces or areas.
-
E.
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.
- 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_69f34995b81c8190acdb45cea5a10eff |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:48 a.m.