Papers › CARE-MI: Chinese Benchmark for Misinformation Evaluation in Maternity and Infant Care

CARE-MI: Chinese Benchmark for Misinformation Evaluation in Maternity and Infant Care

4 Jul 2023NeurIPS 2023 11arXiv:2307.01458archive 2025-07-28

Tong Xiang, Liangzhi Li, Wangyue Li, Mingbai Bai, Lu Wei, Bowen Wang, Noa Garcia

The recent advances in natural language processing (NLP), have led to a new trend of applying large language models (LLMs) to real-world scenarios. While the latest LLMs are astonishingly fluent when interacting with humans, they suffer from the misinformation problem by unintentionally generating factually false statements. This can lead to harmful consequences, especially when produced within sensitive contexts, such as healthcare. Yet few previous works have focused on evaluating misinformation in the long-form (LF) generation of LLMs, especially for knowledge-intensive topics. Moreover, although LLMs have been shown to perform well in different languages, misinformation evaluation has been mostly conducted in English. To this end, we present a benchmark, CARE-MI, for evaluating LLM misinformation in: 1) a sensitive topic, specifically the maternity and infant care domain; and 2) a language other than English, namely Chinese. Most importantly, we provide an innovative paradigm for building LF generation evaluation benchmarks that can be transferred to other knowledge-intensive domains and low-resourced languages. Our proposed benchmark fills the gap between the extensive usage of LLMs and the lack of datasets for assessing the misinformation generated by these models. It contains 1,612 expert-checked questions, accompanied with human-selected references. Using our benchmark, we conduct extensive experiments and found that current Chinese LLMs are far from perfect in the topic of maternity and infant care. In an effort to minimize the reliance on human resources for performance evaluation, we offer off-the-shelf judgment models for automatically assessing the LF output of LLMs given benchmark questions. Moreover, we compare potential solutions for LF generation evaluation and provide insights for building better automated metrics.

PaperPDFConference PDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 14 code samples harvested from 1 repository linked to this paper: 8 ran (of which 0 constructed an object rather than computing a result; 8 with no instrument failure: 0 honoured, 0 violated, 8 with no contract checked; 0 where Syntology's instrument failed) · 6 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 14 samples from 1 repository, 8 ran (8 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written on 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

meetyou-ai-lab/care-mi officialmentioned in papermentioned on GitHubtfApache-2.0Syntology: 14 samples, 8 ran (0 instrument-failed) · 6 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

14 samples harvested: 8 ran (of which 0 constructed an object rather than computing a result; 8 with no instrument failure: 0 honoured, 0 violated, 8 with no contract checked; 0 where Syntology's instrument failed) · 6 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

8ran
6unverified

Licence: 0 of the 14 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from meetyou-ai-lab/care-mi. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

meetyou-ai-lab/care-mi official repository 14 samples, 8 ran (0 instrument-failed) · 6 unverified
CPUBMED_STATEMENT_TEMPLATES_ care-mi/triple2d.py ran Apache-2.0 (permissive) · 98deaa03ee98130c · report fixture: signature rel:str/0/str, head:str/0/str, tail:str/0/str · returned str · level recorded 2026-09-26
extract_similar_substring_ care-mi/replacement.py ran fingerprinted Apache-2.0 (permissive) · d18ad6107d58f2d4 · report fixture: signature source:str/0/str, string:str/0/str · returned float · level recorded 2026-09-26
load_json in 344 papers care-mi/utils.py ran Apache-2.0 (permissive) · 9e4de2d7b7dc59de · report fixture: signature f_path:str/0/str · returned dict · level recorded 2026-09-26
load_jsonl in 179 papers care-mi/utils.py ran Apache-2.0 (permissive) · 9b7a553a1ddf8251 · report fixture: signature file_path:str/0/str, encoding:str/0/str · returned list · level recorded 2026-09-26
load_sheet care-mi/utils.py ran Apache-2.0 (permissive) · 6417cf585bd60864 · report fixture: signature fp:str/0/str, converters:dict/0/?, encoding:str/0/str · returned DataFrame · level recorded 2026-09-26
postprocess in 70 papers
census: 5 implementations from 5 papers, 5 distinct outputs across 2 buckets, one shared input per bucket
care-mi/qg.py ran fingerprinted Apache-2.0 (permissive) · 55566ef834f141a5 · report fixture: signature text:str/0/str · returned str · level recorded 2026-09-26
preprocess in 284 papers
census: 11 implementations from 13 papers, 10 distinct outputs across 5 buckets, one shared input per bucket
care-mi/qg.py ran fingerprinted Apache-2.0 (permissive) · 50d2fce0fe45fd31 · report fixture: signature text:str/0/str · returned str · level recorded 2026-09-26
replace_last_appear_ care-mi/replacement.py ran fingerprinted Apache-2.0 (permissive) · f7735c405412ff58 · report fixture: signature statement:str/0/str, pattern:str/0/str, replace_item:str/0/str · returned str · level recorded 2026-09-26
get_chat_input_ care-mi/negation.py unverified Apache-2.0 (permissive) · a90498c153546f68 · report
get_chat_input_ care-mi/qa2d.py unverified Apache-2.0 (permissive) · e13574c563122e9e · report
negation_api_call_ care-mi/negation.py unverified Apache-2.0 (permissive) · 34725ec2d6ae874e · report
negation_async_ care-mi/negation.py unverified Apache-2.0 (permissive) · f50192fb07c0fe55 · report
qa2d_api_call_ care-mi/qa2d.py unverified Apache-2.0 (permissive) · 716813de8c8087d1 · report
qa2d_async_ care-mi/qa2d.py unverified Apache-2.0 (permissive) · 1e2a7dc94274514a · report

Tasks

Misinformation

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections