COULD JUPITER OR SATURN HAVE EJECTED A FIFTH GIANT PLANET?
Bibliographic record
Abstract
Models of the dynamical evolution of the early solar system that follow the dispersal of the gaseous protoplanetary disk have been widely successful in reconstructing the current orbital configuration of the giant planets. Statistically, some of the most successful dynamical evolution simulations have initially included a hypothetical fifth giant planet, of ice giant (IG) mass, which gets ejected by a gas giant during the early solar system's proposed instability phase. We investigate the likelihood of an IG ejection (IGE) event by either Jupiter or Saturn through constraints imposed by the current orbits of their wide-separation regular satellites Callisto and Iapetus, respectively. We show that planetary encounters that are sufficient to eject an IG often provide excessive perturbations to the orbits of Callisto and Iapetus, making it difficult to reconcile a planet ejection event with the current orbit of either satellite. Quantitatively, we compute the likelihood of reconciling a regular Jovian satellite orbit with the current orbit of Callisto following an IGE by Jupiter of ∼42%, and conclude that such a large likelihood supports the hypothesis of a fifth giant planet's existence. A similar calculation for Iapetus reveals that it is much more difficult for Saturn to have ejected an IG and reconciled a Kronian satellite orbit with that of Iapetus (likelihood ∼1%), although uncertainties regarding the formation of Iapetus, with its unusual orbit, complicates the interpretation of this result.
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.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 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".