aceChatGPT Versus DeepSeek in Resectability Categorization of Chronic Rhinosinusitis: A Comparison Based on EPOS 2020
Objective To evaluate and compare the performance of ChatGPT-5.5 (2026) and DeepSeek-V3 (2026) in classifying CRS resectability according to the EPOS 2020 guidelines, employing various prompting strategies. Methods In this retrospective study, 150 chronic rhinosinusitis cases were reviewed, and three rhinology experts classified resectability according to the EPOS 2020 criteria. GPT-5.5 and DeepSeek-V3 were evaluated using default-knowledge, in-context, and chain-of-thought (CoT) prompting based on accuracy, sen…
With chain-of-thought prompting, both GPT-5.5 and DeepSeek-V3 reached similarly high accuracy in classifying chronic rhinosinusitis resectability, and AI-generated reports raised ENT residents' accuracy to 97.3% in the GPT-5.5 arm versus 72.8% unassisted.
Models were not shown to be ready for routine use: DeepSeek-V3 gave heterogeneous results across subgroups, default-knowledge accuracy was only 72.7% for GPT-5.5, and the authors call for further validation before widespread clinical implementation.
The authors state that the models should be further validated as support tools before widespread clinical implementation, and DeepSeek-V3 showed heterogeneous subgroup responses.
Evidence
- Peer-reviewedWorld Journal of Otorhinolaryngology - Head and Neck Surgery2026-10-08
How should this claim be treated?
Truvace Impact Record TRV-2026-1612, v1: “ChatGPT Versus DeepSeek in Resectability Categorization of Chronic Rhinosinusitis: A Comparison Based on EPOS 2020.” Truvace, 2026-10-16. /record/TRV-2026-1612 (accessed at citation time). sha256 b18b6d0960b3ed84…
Calibration history
Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.
Certified into the record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-1612 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.