Persistence and retention of active ingredients in four granular cholinesterase-inhibiting insecticides in agricultural soils of the lower Fraser River valley, British Columbia, Canada, with implications for wildlife poisoning
Bibliographic record
Abstract
Abstract The persistence and retention of active ingredients in granules of Thimet 15G (phorate 15% by weight), Dyfonate 10G (fonofos 10% by weight), Counter 15G (terbufos 15% by weight), and Furadan 10G (carbofuran 10% by weight) were determined in silt loam and organic muck agricultural soils typical of the lower Fraser River valley (BC, Canada). In June 1995, treatment bags made of polyester cloth (7.5 × 7.5 cm) containing granules of a single insecticide, either alone or with soil, were placed during spring planting in the bottom of the furrow and retrieved periodically until April 1996. The parent component of each insecticide declined monotonically except for carbofuran (logistic decline). In the silt loam (organic muck) soil, the average June-to-October first-order rate constants and half-lives were 0.009 (0.010)/d and 80 (71) d for fonofos, 0.012 (0.009)/d and 58 (82) d for phorate, and 0.032 (0.015)/d and 21 (47) d for terbufos; the half-life of carbofuran was 129 (97) d. By December, the average amounts of fonofos and phorate in silt loam (organic muck) were 26% (range: 17–40%; 14% [range: 3.4–21%]) and 21% (range: 15–30%; 10% [range: 5.0–24%]) of the initial amounts of active ingredients measured at time zero, respectively. By April, the percentages dropped to 16% (range: 7.8–24%; 2.3% [range: 0–7.7%]) and 7.3% (range: 1.9–25%; 0.6% [range: 0–1.9%]). During this period, about 95% of the active ingredients were granule bound, the rest remaining in the bag. Only low levels of terbufos and carbofuran persisted in both soils from December to April of the following year. Results indicate an enhanced probability for poisoning of waterfowl and raptors because of the high levels of active ingredients retained on granules of all four insecticides in both soils in the fall. The risk of acute poisoning by phorate and fonofos continued though the winter.
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.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 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".