MétaCan
Menu
Back to cohort

Collapse of the Quebec Bridge, 1907

2006· article· en· W2123781005 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

VenueJournal of Performance of Constructed Facilities · 2006
Typearticle
Languageen
FieldEngineering
TopicStructural Engineering and Vibration Analysis
Canadian institutionsnot available
FundersNational Science Foundation
KeywordsChord (peer-to-peer)Forensic engineeringEngineeringBridge (graph theory)PierSpan (engineering)Structural engineeringShouldersBeam bridgeCivil engineeringComputer science

Abstract

fetched live from OpenAlex

In the late 19th century, the transportation needs of Quebec led to proposals for bridging the St. Lawrence River. The Quebec Bridge was the longest cantilever structure attempted until that time. In its final design, the clear span was 548.6 m (1,800 ft) long. The bridge project was financially troubled from the beginning. This caused many setbacks in the design and construction. Construction finally began in October 1900. In August 1907, the bridge collapsed suddenly. Seventy five workers were killed in the accident, and there were only 11 survivors from the workers on the span. A distinguished panel was assembled to investigate the disaster. The panel’s report found that the main cause of the bridge’s failure was improper design of the latticing on the compression chords. The collapse was initiated by the buckling failure of Chord A9L, on the anchor arm near the pier, immediately followed by Chord A9R. Theodore Cooper had been the consulting engineer for the Quebec Bridge project, and most of the blame for the disaster fell on his shoulders. He mandated unusually high allowable stresses, and failed to require recalculation of the bridge dead load when the span was lengthened.

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: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.775
Threshold uncertainty score0.289

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.004
GPT teacher head0.168
Teacher spread0.164 · 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