MétaCan
Menu
Back to cohort
Record W2053123825 · doi:10.1016/j.yqres.2011.10.008

Rapid late Pleistocene/Holocene uplift and coastal evolution of the southern Arabian (Persian) Gulf

2011· article· en· W2053123825 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.

fundA Canadian funder is recorded on the work.
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

VenueQuaternary Research · 2011
Typearticle
Languageen
FieldEarth and Planetary Sciences
TopicGeology and Paleoclimatology Research
Canadian institutionsnot available
FundersU.S. Geological SurveyUniversity of WaterlooUniversity of Oxford
KeywordsGeologyPleistoceneHoloceneShorePaleontologyOceanographyGlacial periodSubsidenceSea levelLast Glacial MaximumGeomorphologyPhysical geographyGeography

Abstract

fetched live from OpenAlex

The coastline along the southern Arabian Gulf between Al Jubail, Kingdom of Saudi Arabia, and Dubai, UAE, appears to have risen at least 125 m in the last 18,000 years. Dating and topographic surveying of paleo-dunes (43–53 ka), paleo-marine terraces (17–30 ka), and paleo-marine shorelines (3.3–5.5 ka) document a rapid, > 1 mm/a subsidence, followed by a 6 mm/a uplift that is decreasing with time. The mechanism causing this movement remains elusive but may be related to the translation of the coastal area through the backbasin to forebulge hinge line movement of the Arabian plate or, alternatively, by movement of the underlying Infracambrian-age Hormuz salt in response to sea-level changes associated with continental glaciation. Independent of the mechanism, rapid and episodic uplift may impact the design of engineering projects such as nuclear power plants, airports, and artificial islands as well as the interpretation of sedimentation and archeology of the area.

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.014
Threshold uncertainty score0.998

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.000
Science and technology studies0.0000.001
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0030.001

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.072
GPT teacher head0.273
Teacher spread0.202 · 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