Crash Severity Prediction Using Two-Layer Ensemble Machine Learning Model for Proactive Emergency Management
Bibliographic record
Abstract
Many unfortunate victims in road traffic crashes do not receive ideal treatment because their injury severity is not understood at an early stage. Swift crash severity prediction enables trauma and emergency centers to estimate the potential damage resulting from a road traffic crash and accordingly dispatch the proper emergency units to provide appropriate emergency treatment. A two-layer ensemble machine learning model is proposed in this study to predict road traffic crash severity. The first layer integrates four base machine learning models: k-nearest neighbor, decision tree, adaptive boosting, and support vector machine; the second layer classifies the crash severity based on the feedforward neural network model. The models are developed using road traffic crash data of road intersections over 6 years (2011-2016) obtained from Great Britain's Department of Transport online database. Only the crash features that can be instantaneously and easily obtained are used as an input. To simplify the two-layer ensemble model, principal component analysis technique is used for dimensionality reduction in the second layer of the model. The performance of the two-layer ensemble model is compared with five base models: k-nearest neighbor, decision tree, adaptive boosting, support vector machine, and feedforward neural network. The prediction results reveal that the two-layer ensemble model outperforms the five base classification models based on two performance indicators: testing accuracy and F1 score. The transferability of the developed model is tested using the 3-year crash dataset for Canada obtained from the National Crash Database Online. The outcome indicates that the two-layer ensemble model shows the best performance for the Canadian dataset also. The proposed two-layer ensemble model would be beneficial in predicting crash severity with high accuracy based on limited initial crash information obtained from the crash location. Using this information, trauma centers would be able to prepare for appropriate and prompt medical treatment.
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.002 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| 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".