MétaCan
Menu
Back to cohort
Record W3205057944 · doi:10.1080/23789689.2021.1980299

A comparison of concrete quantities for highway bridge projects: preconstruction estimates vs onsite records

2021· article· en· W3205057944 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.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.
fundA Canadian funder is recorded on the work.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueSustainable and Resilient Infrastructure · 2021
Typearticle
Languageen
FieldEngineering
TopicInfrastructure Maintenance and Monitoring
Canadian institutionsUniversity of Toronto
FundersNatural Sciences and Engineering Research Council of CanadaOntario Centres of Excellence
KeywordsScheduleBridge (graph theory)Cost estimateEstimationTransport engineeringCivil engineeringDuration (music)EngineeringEnvironmental scienceComputer science

Abstract

fetched live from OpenAlex

This paper compares onsite concrete quantities to preconstruction estimates for 18 highway bridges in Canada to quantify the differences in quantities and to identify the driving factors. Material estimates completed during planning and design play a crucial role in predicting project cost, duration, and embodied CO2e emissions for construction projects. However, there is limited understanding of estimating material quantities for construction projects, and their impacts on other estimating processes, e.g., project cost, project schedule, embodied CO2e assessments. Results show that 3–87% greater concrete quantities are used onsite compared to estimates, with the bridges’ substructures responsible for most of the discrepancy. The findings of this study inform our understanding of the preconstruction estimates and their interpretation. Adjusting for the discrepancy between estimates and onsite measurements as well as targeting the drivers of unexpected material use has the potential to reduce environmental impacts, minimize cost overruns, and limit project delays.

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: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.547
Threshold uncertainty score0.998

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.010
GPT teacher head0.261
Teacher spread0.251 · 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