DeepSurvey-Bench: Evaluating Academic Value of Automatically Generated Scientific Surveys

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

arXiv:2601.15307v2 Announce Type: replace-cross Abstract: The rapid development of automated survey generation technology has made it increasingly important to establish a comprehensive benchmark to evaluate the quality of generated surveys. Most existing benchmarks first construct ground-truth datasets by selecting human-written surveys based on limited selection criteria, such as citation counts and structural coherence, and evaluate generated surveys primarily based on conventional quality dimensions, including structural quality and reference relevance. However, these benchmarks have two key issues: (1) the datasets are insufficiently reliable because the selection criteria only identify highly cited or structurally coherent surveys without verifying their academic value; (2) the evaluation metrics mainly reflect the surface-level quality of generated surveys and are insufficient to assess their academic value. Together, these issues prevent existing benchmarks from effectively assessing the academic value of generated surveys. To address the above problems, we propose DeepSurvey-Bench, a comprehensive benchmark for evaluating the academic value of automatically generated surveys. Specifically, our proposed benchmark introduces a set of academic value evaluation criteria covering three dimensions: informational value, scholarly communication value, and research guidance value. We first construct a reliable dataset with academic value annotations based on these criteria, and then evaluate the academic value of generated surveys according to these criteria through a …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://arxiv.org/abs/2601.15307
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.