MétaCan
Menu
Back to cohort

The Chicago–East Coast Corridor: Changing Intermodal Patterns

2012· article· en· W2132058590 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

aboutThe title or abstract carries a Canadian signal from the geographic lexicon.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueTransportation Journal · 2012
Typearticle
Languageen
FieldEngineering
TopicUrban and Freight Transport Logistics
Canadian institutionsnot available
Fundersnot available
KeywordsEast coastTruckGeographyTraffic flow (computer networking)West coastTransport engineeringEngineeringOceanographyPhysical geographyGeology

Abstract

fetched live from OpenAlex

Abstract The Chicago–East Coast Corridor is a network of highways and railroad tracks connecting Chicago to cities on the East Coast. Cargos flow through it in both directions—Asian cargos flow from West Coast ports through Chicago for eastward delivery, and cargos from India and Europe flow from East Coast seaports to Chicago and beyond for westward delivery. This heavily used Corridor is currently expanding in both capacity and service offerings. However, two areas of the Corridor, Detroit and Northeast Ohio, remain less well served. The article outlines the changes taking place and suggests opportunities that might benefit these two areas. In particular, the St. Lawrence Seaway is part of an all-water minimum-mileage route between the Midwest and Rotterdam and Antwerp. This underutilized and almost forgotten route, if used, would eliminate a significant amount of rail and truck traffic to Detroit and Northeast Ohio. Further, increased rail deliveries from Halifax and Montreal to Detroit would allow Detroit to develop a substantial rail hub, reducing its truck deliveries from Chicago. Both suggestions would significantly reduce trucking in the Corridor.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.370
Threshold uncertainty score0.449

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.019
GPT teacher head0.200
Teacher spread0.180 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it