Junxian He, Pengfei Liu, Yiran Zhao, Jinghan Zhang, Shiqi Chen, I-Chun Chern, Siyang Gao
We have not lifted any functions out of this paper's repositories yet, so there is nothing we have run. The repositories linked to it are listed below.
Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.
Assessing factuality of text generated by large language models (LLMs) is an emerging yet crucial research area, aimed at alerting users to potential errors and guiding the development of more reliable LLMs. Nonetheless, the evaluators assessing factuality necessitate suitable evaluation themselves to gauge progress and foster advancements. This direction remains under-explored, resulting in substantial impediments to the progress of factuality evaluators. To mitigate this issue, we introduce a benchmark for Factuality Evaluation of large Language Models, referred to as FELM. In this benchmark, we collect responses generated from LLMs and annotate factuality labels in a fine-grained manner. Contrary to previous studies that primarily concentrate on the factuality of world knowledge (e.g. information from Wikipedia), FELM focuses on factuality across diverse domains, spanning from world knowledge to math and reasoning. Our annotation is based on text segments, which can help pinpoint specific factual errors. The factuality annotations are further supplemented by predefined error types and reference links that either support or contradict the statement. In our experiments, we investigate the performance of several LLM-based factuality evaluators on FELM, including both vanilla LLMs and those augmented with retrieval mechanisms and chain-ofthought processes. Our findings reveal that while retrieval aids factuality evaluation, current LLMs are far from satisfactory to faithfully detect factual errors. 1 * Work done during visiting HKUST. 1 The FELM dataset is available at https://github.com/hkust-nlp/felm. 37th Conference on Neural Information Processing Systems (NeurIPS 2023) Track on Datasets and Benchmarks.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2310.00741")
get_code_for_paper("2310.00741")
have("2310.00741")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2310.00741.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2310.00741)
Connect an agent — have() is free.