aceModerate evidence
Published recordEducationProblem Space
More
From boredom to problematic AI chatbot use: a three-wave half-longitudinal mediation study of loneliness and dual-system self-control
- Truvace record
- TRV-2026-2530raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Observational study
- Sources
- 1 sourcePeer-reviewed
- sha256
- e1b90517ab34…check it
Background: Problematic use of AI chatbots (PUAIC) is an emerging concern. Drawing on the I-PACE model and the dual-system model of self-control, this study examined the mediating roles of loneliness, the control system, and the impulsive system. Methods: A three-wave half-longitudinal mediation design was used with 551 Chinese college students at baseline. Boredom proneness was assessed at Time 1, loneliness and the control and impulsive systems at Time 2, and PUAIC at Time 3. Missing data were handled using 20…
The problem
In a three-wave study of 551 Chinese college students, higher boredom proneness was associated with more problematic AI chatbot use two months later, directly (β = .25) and through loneliness and impulsive tendencies.
What this doesn’t fix
Boredom proneness, mediators and problematic use were each measured at only one wave, with no baseline controls, so causal and change-over-time conclusions are ruled out; the sample was convenience-based, from two Chinese universities, and relied on self-report.
Sources
1 on file- Australian Journal of Psychologydoi:10.1080/00049530.2026.2737094
Cite this record
v1Truvace Impact Record TRV-2026-2530, v1: “From boredom to problematic AI chatbot use: a three-wave half-longitudinal mediation study of loneliness and dual-system self-control.” Truvace, 2026-11-12. /record/TRV-2026-2530 (accessed on the day you copy it). sha256 e1b90517ab3435b8…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2530 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.