TRV-2026-1621Certified recordPeer-reviewed

Ensemble of Domain-Specific Natural Language Processing and Large Language Models for Detecting Suicidal Ideation and Mental Health Conditions in Social Media Text: Development and Evaluation Study

Background Mental illness contributes substantially to global disability, and public adoption of AI for mental health support is accelerating without commensurate safety evaluation. General-purpose large language models can fail to recognize naturalistic text expressing suicidal ideation, with immediate clinical consequences. Domain-specific natural language processing methods offer a contrasting approach, but ensembles integrating the two have not been formally characterized. Objective We aimed to (1) benchmark…

Health · Good Space — documented gain · certified 2026-10-16 · v1 · article view · machine-readable

Current reading — gain

Combining a domain-specific classifier with a fine-tuned language model at a 60/40 weighting reached about 93.9% test accuracy, above either model used alone on this Reddit and Twitter corpus.

What this doesn’t fix

Labels were community-inferred rather than clinical diagnoses and only one corpus was analyzed, so the results are hypotheses needing external validation on clinically characterized data before use in decision support.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1621, v1: “Ensemble of Domain-Specific Natural Language Processing and Large Language Models for Detecting Suicidal Ideation and Mental Health Conditions in Social Media Text: Development and Evaluation Study.” Truvace, 2026-10-16. /record/TRV-2026-1621 (accessed at citation time). sha256 60883f352abaac84…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv160883f352aba…

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1621 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.