Tajik Basin and Southwestern Tian Shan, Northwestern India‐Asia Collision Zone: 2. Timing of Basin Inversion, Tian Shan Mountain Building, and Relation to Pamir‐Plateau Advance and Deep India‐Asia Indentation
Bibliographic record
Abstract
Abstract The Tajik basin and southwestern Tian Shan constitute the northwestern tip of the India‐Asia collision zone. Basin inversion formed the thin‐skinned Tajik fold‐thrust belt, outlined by westward convex fold trains, underlain by a décollement in Jurassic evaporites. The belt's leading edge—the Uzbek Gissar—and its transpressional northern lateral margin—the Tajik Gissar—constitute the thick‐skinned foreland buttresses. Apatite fission‐track data indicate ~40‐ to 15‐Ma reheating by sediment burial in the Tian Shan. In the Gissar and the Tajik fold‐thrust belt, apatite fission‐track and (U,Th)/He ages date the major phase of shortening/erosion between ~12 and 1 Ma, with exhumation to 2‐ to 3‐km crustal depths within a few Myr after onset of shortening. Shortening spread immediately across the fold‐thrust belt, typical for belts floored by a detachment in ductile rocks, and into the foreland buttresses. Reactivation concentrated in the internal (eastern) fold‐thrust belt with the thickest evaporates. The youngest ages (~6.6–1.6 Ma) occur along the Vakhsh thrust, the active erosional front of the fold‐thrust belt in the northeastern Tajik basin, where it narrows between the converging Tian Shan and Pamir. Our study links major events in the Pamir hinterland with the Tajik basin and Tian Shan foreland. In the late Eocene–early Miocene, the advancing Pamir‐plateau crust loaded the foreland, inducing subsidence, reheating, and early shortening. Basin inversion and major shortening/transpression in the foreland buttresses from ~12 Ma onward were synchronous with the subcrustal indentation of Indian lithosphere into the Tajik‐Tarim basin lithosphere and the onset of its rollback beneath the Pamir.
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.002 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.002 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".