MétaCan
Menu
Back to cohort
Record W2104311334 · doi:10.1306/103000710537

The Castlegate Sandstone of the Book Cliffs, Utah: Sequence Stratigraphy, Paleogeography, and Tectonic Controls

2001· article· en· W2104311334 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.

Bibliographic record

VenueJournal of Sedimentary Research · 2001
Typearticle
Languageen
FieldEarth and Planetary Sciences
TopicGeological formations and processes
Canadian institutionsUniversity of Toronto
Fundersnot available
KeywordsGeologyPalaeogeographySequence (biology)StratigraphyTectonicsSequence stratigraphyPaleontologyFaciesStructural basinVolcanism

Abstract

fetched live from OpenAlex

Abstract Earlier stratigraphic work had predicted that at the type section of the Castlegate Formation, the Castle Gate, near Price, Utah, the unit consists of two sequences separated by a sequence boundary representing approximately one million years of unrecorded time. Although the type section is well exposed, it consists of a monotonous succession of braided fluvial sandstones and no obvious boundary can be identified using facies criteria—this is a good example of a "cryptic sequence boundary." Petrographic data indicate, however, a significant change in detrital composition 20 m above the base of the section, at a through-going erosion surface that is therefore interpreted as the sequence boundary. Revised sequence correlations, together with other petrographic data and regional paleocurrent patterns, provide the basis for a model of the paleogeographic evolution of the area. Rocks assigned to the Castlegate Sandstone comprise two or possibly three sequences formed at times of slow regional subsidence. Erosional sequence boundaries and tilts in paleoslope between each sequence record thrust loading and unloading of the basin and the growing influence of intrabasinal upwarps, movement of which was beginning to be affected by Laramide movements toward the end of Castlegate sedimentation.

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.002
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.050
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0010.001
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0010.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.056
GPT teacher head0.315
Teacher spread0.259 · 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