MétaCan
Menu
Back to cohort
Record W2336162649 · doi:10.1515/pac-2015-0802

How to name new chemical elements (IUPAC Recommendations 2016)

2016· article· en· W2336162649 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

VenuePure and Applied Chemistry · 2016
Typearticle
Languageen
FieldChemistry
TopicHistory and advancements in chemistry
Canadian institutionsNational Research Council Canada
Fundersnot available
KeywordsChemical nomenclatureChemistryGroup (periodic table)Consistency (knowledge bases)Element (criminal law)Organic chemistryComputer scienceLaw

Abstract

fetched live from OpenAlex

Abstract A procedure is proposed to name new chemical elements. After the discovery of a new element is established by the joint IUPAC-IUPAP Working Group, the discoverers are invited to propose a name and a symbol to the IUPAC Inorganic Chemistry Division. Elements can be named after a mythological concept, a mineral, a place or country, a property or a scientist. After examination and acceptance by the Inorganic Chemistry Division, the proposal follows the accepted IUPAC procedure and is then ratified by the Council of IUPAC. This document is a slightly amended version of the 2002 IUPAC Recommendations; the most important change is that the names of all new elements should have an ending that reflects and maintains historical and chemical consistency. This would be in general “-ium” for elements belonging to groups 1–16, i.e. including the f-block elements, “-ine” for elements of group 17 and “-on” for elements of group 18.

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.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Insufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: Bench or experimental
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.381
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0050.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.252
Teacher spread0.240 · 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