MétaCan
Menu
Back to cohort
Record W2016231461 · doi:10.1111/ter.12112

Building the Hindu Kush: monazite records of terrane accretion, plutonism and the evolution of the Himalaya–Karakoram–Tibet orogen

2014· article· en· W2016231461 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

VenueTerra Nova · 2014
Typearticle
Languageen
FieldEarth and Planetary Sciences
TopicGeological and Geochemical Analysis
Canadian institutionsUniversity of SaskatchewanOkanagan University CollegeUniversity of British Columbia, Okanagan CampusUniversity of British Columbia
Fundersnot available
KeywordsGeologyTerraneBatholithPaleontologyPlutonismCretaceousIsland arcMetamorphismCenozoicMonaziteAccretion (finance)Back-arc basinGeochemistryTectonicsSubductionZirconStructural basinPluton

Abstract

fetched live from OpenAlex

Abstract In situ U‐Th/Pb ( LA ‐ ICP ‐ MS ) monazite ages from the Hindu Kush of NW Pakistan provide new petrochronologic constraints on the tectonic evolution of the Himalaya–Karakoram–Tibet orogen. Monazites from two adjacent garnet + staurolite schist specimens yield multiple age populations that record the major Mesozoic and Cenozoic deformational, magmatic and metamorphic events along the southern margin of Eurasia. These include the accretion of the Hindu Kush– SW Pamir to Eurasia during the Late Triassic, followed by the accretion of the Karakoram terrane in the Early Jurassic. Younger Jurassic and Cretaceous ages record the development of an Andean‐style volcanic arc along the southern Eurasian margin, which ended with the docking of the Kohistan island arc and the emplacement of the Kohistan–Ladakh batholith during the Late Cretaceous. The initial Eocene collision of India with Eurasia was followed by widespread high‐temperature metamorphism and anatexis associated with crustal thickening within the Himalaya system in the Late Oligocene and Early Miocene.

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 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.085
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.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.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0020.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.012
GPT teacher head0.199
Teacher spread0.187 · 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