Functional flower traits and their diversity drive pollinator visitation
Bibliographic record
Abstract
Recent studies have shown that the diversity of flowering plants can enhance pollinator richness and visitation frequency and thereby increase the resilience of pollination. It is assumed that flower traits explain these effects, but it is still unclear which flower traits are responsible, and knowing that, if pollinator richness and visitation frequency are more driven by mass‐ratio effects (mean trait values) or by trait diversity. Here, we analyse a three‐year data set of pollinator observations collected in a European grassland plant diversity experiment (The Jena experiment). The data entail comprehensive flower trait measurements, including reward traits (nectar and pollen amount), morphological traits (height, symmetry, area, colour spectra) and chemical traits (nectar‐amino acid and nectar‐sugar concentration). We test if pollinator species richness and visitation frequency of flower communities depend on overall functional diversity combining all flower traits within a community, single trait diversities (within trait variation) and community‐weighted means of the single traits, using Bayesian inference. Overall functional diversity did not affect pollinator species richness, but reduced visitation frequency. When looking at individual flower traits separately, we found that single trait diversity of flower reflectance and flower morphology were important predictors of pollinator visitation frequency. Moreover, independent of total flower abundance, community‐weighted means of flower height, area, reflectance, nectar‐sugar concentration and nectar‐amino acid concentration strongly affected both pollinator species richness and visitation frequency. Our results, challenge the idea that functional diversity always positively affects ecosystem functions. Nonetheless, we demonstrate that both single trait diversity and mass‐ratio effects of flower traits play an important role for diverse and frequent flower visits, which underlines the functionality of flower traits for pollination services.
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.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 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".