Bibliographic record
Abstract
The benefits system has grown progressively more complex. Some of that complexity is intrinsic: the design of benefits can be complex in its conception, its operation and its structure. Some of it comes from the interaction of different benefits, the complexity of the rules that are applied, and the practical difficulties of managing a system for millions of people. Part, however, reflects the complexity of people’s circumstances and needs. Despite periodic attempts to simplify the system, it is difficult to do this in a way that will not imply considerable problems for benefits and for the people who receive them. Some of the complexity is avoidable, but much is not. Why is the benefits system so complicated? Part of the answer is historical: the benefits system has simply grown this way. Part is practical. The problem with trying to change it is that, without a great deal more money, changes can only be made by taking money from some people and giving it to others. That would mean that some very poor people are made worse off. The idea of simplifying benefits returns periodically to the policy agenda. It was on the agenda in the 1970s, with the Conservative Tax Credit scheme1 and the reform of ‘social assistance’, and in the 1980s with the Fowler Reviews, and it has been central to the proposals for Universal Credit. But an understanding of complexity is essential before we can work out where some simplification might be possible. In a report published in 2005, the National Audit Office identified five types of complexity: problems of changing design, patchwork changes, horizontal links between benefits, vertical interfaces (between higher and lower levels of the administration) and ‘delivery interactions’, between the service and the user.
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.002 | 0.006 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.003 | 0.002 |
| Science and technology studies | 0.003 | 0.013 |
| Scholarly communication | 0.009 | 0.015 |
| Open science | 0.001 | 0.006 |
| Research integrity | 0.002 | 0.003 |
| Insufficient payload (model declined to judge) | 0.024 | 0.003 |
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".