The Colombian geochronological database (CGD)
Bibliographic record
Abstract
Geochronological databases are powerful tools for characterizing the crustal evolution and the age spectra of a region and allow comparison with other areas at a regional scale. In this contribution, we present the Colombian Geochronological Database (CGD), which contains a curated compilation of ca. 67,406 individual published U-Th-Pb, K-Ar, Ar-Ar, Rb-Sr, Sm-Nd, Lu-Hf, Fission-track, U-Th-He, and Re-Os mineral and whole rock ages that are reported in the published literature. Each date includes geographic coordinates, geological setting, petrologic and chemical information extracted from the respective publications. The structure of the database provides a powerful interface for constructing queries and allows searching and extracting information on geographic domains, provinces, stratigraphic units, isotopic systems, date interpretations, references, etc. This information establishes a framework for regional and global geological interpretations with geochronological, stratigraphic, structural and palaeogeographic implications.With the present effort we present to the geoscience community a clear insight, from a regional perspective, to the geology and tectonics of Colombia since Precambrian times. The comparison of all (detrital and magmatic) single zircon U-Pb dates from the Colombian (Gondwana sourced) geochronological database with the Global and North American (Laurentia sourced) databases provides a temporal constraint on the evolution of the South American continent. U-Pb zircon ages in Colombia define 13 peak clusters centred at 1767, 1530, 1325, 1178, 1007, 605,540, 468, 271, 237, 182, 76 and 10 Ma but of those, only few have a good correlation in all three databases: 1007 (Grenvillian/Orinoquian/Putumayo Orogeny), 605 (Braziliano/Pan-African Orogeny), 468 (Famatinian/Taconic Orogeny), and 182 Ma (Break-up of Pangea) zircon peaks. This correlation suggests that some tectonic events in Colombia are global and might represent crustal production and preservation while the other peaks might just represent local arc magmatic events.
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.001 | 0.006 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.021 | 0.019 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.003 | 0.002 |
| Open science | 0.002 | 0.002 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.023 | 0.012 |
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".