52/100

Moderate evidence

Published recordBusinessGeneral

Insurance claim level estimation and influencing factor analysis for electric vehicles: A case study in Changsha city

Truvace record
TRV-2026-1106raw data (JSON)
Version
v3Revised
First published
Evidence type
Benchmark or lab evaluation
Sources
1 sourcePeer-reviewed
sha256
9bfc75afdee1…check it

Objectives Claim amount levels reflect severity risk and facilitates risk estimation in insurance practice. This study supports risk management in electric-vehicle traffic insurance by establishing an effective classification framework for claim levels. Methods The Synthetic Minority Over-Sampling Technique (SMOTE) is applied to balance the distribution of claim amount levels in traffic insurance. This study applies six distinct models-Decision Tree, Random Forest, CatBoost, Support Vector Machine (SVM), Multila…

The gain

Machine learning classification improves risk differentiation for electric-vehicle traffic insurance by predicting claim amount levels from policy and behavioral features.

Sources

1 on file
  1. Traffic Injury Preventiondoi:10.1080/15389588.2026.2722335
    Peer-reviewed2026-09-15

Cite this record

v3

Truvace Impact Record TRV-2026-1106, v3: “Insurance claim level estimation and influencing factor analysis for electric vehicles: A case study in Changsha city.” Truvace, 2026-11-04. /record/TRV-2026-1106 (accessed on the day you copy it). sha256 9bfc75afdee16d40…

Change history

3 versions

Every change made to this record since it was first published, and why.

  1. Revisedv39bfc75afdee1…

    Copy cleanup: removed remarks about truncated source text.

  2. Revisedv29b78e76fea1d…

    Direction audit: the gain line stated no AI consequence and was removed. Filed as context; not counted as a gain or a problem.

  3. Publishedv15e16458731f0…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-1106 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.