Bibliographic record
Abstract
On the morning of Monday, October 12, 1931, early risers in northern Portland noticed a strange creature with smooth black skin in Columbia Slough, right next to the Jantzen Beach Amusement Park. Locals debated its identity. Some argued it was a sturgeon, others a sei whale all the way from Japan. Finally, an old salt tagged it as a small “blackfish.” News of the novelty spread like wildfire, drawing thousands of spectators and causing gridlock on the interstate bridge between Portland and Vancouver, Washington. A local newspaper warned that killer whales were one of the ocean’s “most vicious” creatures, but this one promptly stole Portland’s heart. “From the looks of things,” declared Deputy Sheriff Martin T. Pratt, “nearly everyone in the city is determined to see the visitor,” and when some locals began shooting at the animal, Pratt and his men arrested them. The number of sightseers grew each day, and that weekend, tens of thousands crowded into Jantzen Beach to catch a glimpse of the whale, while enterprising fishermen charged twenty-five cents for whale-watching rides. By that time, someone had dubbed the orca Ethelbert, and the name stuck. Why the little whale had arrived there, a hundred miles up the Columbia, remains a mystery. It had probably become separated from its mother and lost its bearings, wandering up the great river that divides western Oregon from Washington State. But Columbia Slough was no place for an orca. In addition to lacking salt water, it was the main outlet for Portland’s sewage. In summer, the waterway grew so foul that workers refused to handle timber passing through it. As the days passed, observers grew worried. The whale seemed sluggish, and its skin began to show unsightly blotches. The owner of Jantzen Beach proposed capturing the animal with a net and placing it in a saltwater tank. It would have been an extraordinary attraction for his amusement park—already known as the Coney Island of the West. But members of the Oregon Humane Society denounced the scheme as rank cruelty. Instead, they proposed blowing the young orca up with dynamite.
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.001 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.005 | 0.001 |
| Scholarly communication | 0.007 | 0.003 |
| Open science | 0.001 | 0.003 |
| Research integrity | 0.002 | 0.003 |
| Insufficient payload (model declined to judge) | 0.556 | 0.340 |
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".