MétaCan
Menu
Back to cohort
Record W2062160031 · doi:10.1139/l09-102

Utility impact rating with subsurface utility engineering in project development

2009· article· en· W2062160031 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.

venuePublished in a venue whose home country is Canada.
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

VenueCanadian Journal of Civil Engineering · 2009
Typearticle
Languageen
FieldEngineering
TopicUnderground infrastructure and sustainability
Canadian institutionsnot available
FundersWashington State Department of TransportationPennsylvania Department of Transportation
KeywordsProcess (computing)Risk analysis (engineering)Service (business)Construction engineeringTransport engineeringComputer scienceEngineeringOperations researchCivil engineeringBusiness

Abstract

fetched live from OpenAlex

A lack of reliable information regarding the locations of underground utilities can not only result in property damage, construction delays, design changes, claims, injuries, and even deaths but can also cause traffic delays, local business disruptions, environmental problems, and utility service breakdowns in highway projects. The subsurface utility engineering (SUE) is an engineering process designed to reduce the potential of underground utility conflicts at the planning phase. The SUE uses new and existing technologies to identify, characterize, and map accurately the underground utilities with three major activities: designation, location, and data management. In this study, a decision-support tool called the SUE utility impact rating form, which refers to utility complexity at the construction site, has been developed to determine which projects should include SUE and the appropriate levels of SUE investigation to be used. In addition, case studies with benefit–cost ratio have been performed to verify the form.

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.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
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.731
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.001
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.006
GPT teacher head0.196
Teacher spread0.190 · 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