Triple
T622066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Trail |
E14534
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 19th-century 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: 19th-century transportation route Context triple: [California Trail, instanceOf, 19th-century transportation route]
-
A.
historic transportation system
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.
-
B.
transportation route
A transportation route is a defined path or corridor used to move people or goods between locations via one or more modes of transport.
-
C.
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.
-
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.
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.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:35 p.m.