Pith. sign in

Reference change · event page

Reference changes · DOI

, keywords =

Published notice on a work cited in the Pith corpus. Exact quotes below. No model judges whether any citation was load-bearing.

This page records that a citing paper's bibliography includes a work with a published notice. It is not a judgment on the citing paper.

Correction Crossref 2 open · 2 total · 0 disputed
DOI
10.3847/1538-4357/adc5f7
Notice DOI
10.3847/1538-4357/adff60
Event date
2025-09-10
Machine twin
JSON

01One-hop citing occurrences

Correction Open
JADES: the mass-metallicity relation at $z=1-10$. New calibrations, extremely metal-poor galaxies, and chemical diversity

ref [242] · 2606.11345 · notice #1760 · dispute

Raw extraction · bibliography line

Exploring the Relationship between Stellar Mass, Metallicity, and Star Formation Rate at z 2.3 in KBSS-MOSFIRE. , keywords =. doi:10.3847/1538-4357/adc5f7 , archivePrefix =. 2503.10800 , primaryClass =

Parser render (TeX stripped for reading; raw above is the evidence)

Exploring the Relationship between Stellar Mass, Metallicity, and Star Formation Rate at z 2.3 in KBSS-MOSFIRE., keywords =. doi:10.3847/1538-4357/adc5f7, archivePrefix =. 2503.10800, primaryClass =

Correction Open
The evolution of the galaxy gas-phase mass-metallicity relation from $z=15$ to $z=0$ in the COLIBRE cosmological simulations

ref [155] · 2606.25995 · notice #1759 · dispute

Raw extraction · bibliography line

Exploring the Relationship between Stellar Mass, Metallicity, and Star Formation Rate at z 2.3 in KBSS-MOSFIRE. , keywords =. doi:10.3847/1538-4357/adc5f7 , archivePrefix =. 2503.10800 , primaryClass =

Parser render (TeX stripped for reading; raw above is the evidence)

Exploring the Relationship between Stellar Mass, Metallicity, and Star Formation Rate at z 2.3 in KBSS-MOSFIRE., keywords =. doi:10.3847/1538-4357/adc5f7, archivePrefix =. 2503.10800, primaryClass =

Status lifecycle on notices: open → disputed → (response attached on the notice page). Repaired counts matter as much as open counts. There is no “safe,” “invalid,” or “resolved” badge.