TRV-2026-1806Version 1 · Certified
Reason for this version
Certified into the record
Canonical text (the exact bytes fingerprinted)
TRUVACE RECORD VERSION record: TRV-2026-1806 version: 1 kind: certified reason: Certified into the record timestamp: 2026-10-18T10:41:42.177700Z status: published lens: g_space sector: policy headline: Evidence-grounded road safety countermeasure recommendation from crash-context queries: A modular LLM framework dek: Traffic safety countermeasure recommendation requires simultaneous consideration of crash context, roadway facility, traffic control, operating conditions, and evidence applicability. Traditional rule-based and keyword-matching methods have difficulty processing natural-language crash-context queries. This study proposes an evidence-grounded and mechanism-aware framework that formulates traffic safety countermeasure recommendation as the construction, selection, and ranking of CMF Evidence Cards. A structured CM… gain_title: A fine-tuned Qwen3-32B framework retrieved and ranked CMF Evidence Cards for crash-context queries, placing the exact evidence in its top three in 76.15% of cases and beating a BM25-RAG baseline. problem_title: (none) trace_subject: (none) gain_reading: A fine-tuned Qwen3-32B framework retrieved and ranked CMF Evidence Cards for crash-context queries, placing the exact evidence in its top three in 76.15% of cases and beating a BM25-RAG baseline. gain_evidence: Exact Evidence Hit@3 of 76.15% | substantially outperformed a conventional BM25-RAG baseline problem_reading: (none) problem_evidence: (none) quick_read: Researchers built a framework that turns natural-language descriptions of crash situations into ranked traffic safety countermeasure recommendations. It draws on a store of 8844 evidence cards derived from the CMF Clearinghouse, narrows the candidates through retrieval, recall augmentation and applicability filtering, and then has a fine-tuned language model pick up to three. The approach matters because rule-based and keyword methods struggle with free-text crash queries, and this one ties each recommendation to its source evidence and applicability conditions. Exact-match accuracy was moderate, though, and the authors report that retrieval remains weak in specialized settings such as work zones. limitation: The authors identify evidence retrieval as a limitation in specialized contexts such as work zones, and exact-evidence top-1 accuracy was only 53.14%. tag: Evidence-backed gain key_points: The evidence store holds 8844 Evidence Cards, tested against 2935 crash-context queries that include 1000 deliberately incomplete variants. | The fine-tuned Qwen3-32B reached 53.14% Exact Evidence Top-1 and 83.26% Mechanism Hit@3. | It correctly decided when no evidence applied in 95.08% of empty-set cases. | Evidence coverage in the candidate pool saturated at about 30 Evidence Cards. | Independent expert evaluation supported the relevance and engineering applicability of the recommendations. rundown: The pipeline has three candidate-construction steps: context-aware retrieval, mechanism-aware recall augmentation and engineering applicability filtering. The language model, fine-tuned by supervised learning, then selects and ranks up to three Evidence IDs. Each is returned with a countermeasure description, CMF or CRF values, evidence quality, applicability conditions and literature sources. Ablation tests confirmed that each of the three candidate-construction components contributes distinctly. The framework also stayed stable across semantically equivalent paraphrases of the same query and outperformed a conventional BM25-RAG baseline. Evaluation combined LLM-assisted and independent expert review, which supported contextual relevance, mechanism consistency and overall usefulness. Case studies covered mechanism-complex and facility-specific scenarios. sources: - peer_reviewed | Accident Analysis & Prevention | https://doi.org/10.1016/j.aap.2026.108799 | 2026-10-17 prev: 0000000000000000000000000000000000000000000000000000000000000000
- sha256
- 9d8f739d73dfbc7ebfe84a26f9671f80d732499a5734448d7ad452e214246f08
- previous
- 0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-1806 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.
ace