跳到正文

ReviewPilot:面向系统综述筛查与数据抽取的多智能体系统

摘要

佛罗里达国际大学等机构的研究者提出对话式多智能体系统 ReviewPilot,覆盖系统综述的检索、筛查、全文获取、信息抽取与语义归类五个阶段,研究者可通过对话定制纳入排除标准与抽取字段,每条筛查决定附理由、每个抽取值附原文出处,项目记忆保留配置与修订。

摘要由模型根据原文撰写,以原文为准。

正文 · 原文

Zhaoqian Xue ††thanks: Corresponding authors: Zhaoqian Xue and Lingyao Li.    Shaoze Zhou Affiliation: Florida International University    Xuexin Li Affiliation: Vanderbilt University    Junting Mu Affiliation: University of California, Irvine    Haozheng Liu Affiliation: New York University    Zhongyin Wang Affiliation: University of Illinois Urbana-Champaign    Yichun He Affiliation: Broad Institute of MIT and Harvard    Renkai Ma Affiliation: University of Cincinnati    Hao Zhou Affiliation: University of South Florida    Sarah Bratt Affiliation: University of Arizona    Siyuan Ma Affiliation: Vanderbilt University Medical Center    Chen Chen Affiliation: Florida International University    Lingyao Li22footnotemark: 2 Affiliation: University of Arizona

Abstract

Systematic literature reviews follow the PRISMA process of screening scholarly works and extracting evidence from included studies. Deep research tools based on large language models (LLMs) can search and summarize the literature but do not record which studies are excluded or where extracted values come from. We develop a conversational multi-agent system called ReviewPilot that automates the PRISMA workflow from paper screening to information extraction. Researchers can tailor criteria and schemas through dialogue, and a project memory keeps their configurations and revisions. Each screening decision comes with its reason and each extracted value with its source. On epidemiological expert reviews, ReviewPilot outperforms a single-prompt LLM and AgentSLR across three LLMs, with screening macro F1 up to 0.776 and extraction F1 up to 0.788. Case studies in biomedicine and human-computer interaction show close agreement with human annotators, suggesting that ReviewPilot can transfer beyond epidemiology. Code is available at this link.

1 Introduction

Refer to caption
Figure 1: Manual and ReviewPilot-assisted systematic review workflows, aligned with PRISMA 2020 stages (Page et al., 2021). ReviewPilot coordinates search, screening, and extraction while supporting researcher inspection and revision. Project memory retains configurations, outputs, and corrections.

Systematic literature reviews depend on a sequence of judgments, including eligibility check, full-text retrieval, and information extraction (Higgins et al., 2023; Page et al., 2021). Such a process if labor-intensive. Searches often result in high recall, so reviewers need to read thousands of titles and abstracts to find a few eligible studies (van de Schoot et al., 2021). A review can take over a year on average from registration to publication (Borah et al., 2017). Automation can reduce this workload, but researchers still need to inspect decisions and document the process based on the PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-Analyses) 2020 process (Page et al., 2021).

Large language models (LLMs) are now widely used to search and summarize literature. Deep research tools such as ChatGPT (OpenAI, 2025), Gemini (Citron, 2024), and Perplexity Research (Perplexity, 2025) can generate a synthesized report. These tools help researchers explore a topic but do not follow the PRISMA process. They do not show which papers are screened or excluded and why, or where each extracted value comes from. Other review tools only limit these decisions to a single stage, such as ASReview (van de Schoot et al., 2021) and LGAR (Jaumann et al., 2025) for screening, and RobotReviewer (Marshall et al., 2017) for extraction, or an agent-based system for a few stages like AgentSLR (Padarha et al., 2026).

However, designing an AI-assisted literature review workflow involves two key considerations. First, screening criteria and field definitions need operational instructions. Domain terms and borderline cases need to be iteratively interpreted consistently for screening and coding. Second, outputs must reflect the current configuration. Researchers refine criteria and fields as a review progresses (Higgins et al., 2023); confirmed settings and corrections must therefore be retained, and affected downstream outputs identified. We implement these requirements within a workflow that records the counts and inclusion-exclusion criteria needed for PRISMA-guided workflow.

We present ReviewPilot, a conversational multi-agent system that addresses these challenges from search through information extraction (Figure 1). Researchers define eligibility criteria and an extraction schema through natural dialogue with the system, and a Prompt Agent turns them into review-specific guidance. Agents screen records and extract information, delivering screening decisions with their reasons and extracted values linked to source passages in the papers. The result is a step-by-step record of how papers are filtered, with the records kept and excluded at each stage, and a table of the information extracted from each retrieved paper. Our contributions are as follows.

  • •

    PRISMA-guided workflow. ReviewPilot coordinates search, screening, retrieval, and extraction while recording counts, exclusion reasons, and available source for inspection (Section 3).

  • •

    Review-specific configuration and revision. Researchers can set criteria and schemas through dialogue. Then, agents draft screening guidance and coding rules. Researchers can edit these instructions and confirm. Project memory design further retains these configurations and corrections (Sections 3.2 and 3.6).

  • •

    System-level evaluation. On PERG, ReviewPilot achieves higher screening macro F1 and extraction F1 than a single-prompt LLM and AgentSLR under the reported settings (Tables 1 and 2). Two case studies document completed workflows and screening agreement with human annotators (Section 5).

2 Related Work

LLM multi-agent systems.

Multi-agent frameworks divide tasks among LLM agents with distinct roles (Guo et al., 2024b). For instance, AutoGen supports configurable conversations that combine LLMs, tools, and human input (Wu et al., 2024). MetaGPT encodes standard operating procedures as prompt sequences to coordinate software development and check intermediate results (Hong et al., 2024). Our system, ReviewPilot, leverages the potential of multi-agent workflow to review stages.

Deep research and literature synthesis. Deep research tools in ChatGPT (OpenAI, 2025), Gemini (Citron, 2024), and Perplexity (Perplexity, 2025) iteratively search and analyze sources to produce reports. ChatGPT or Gemini can link citations and allows users to revise its research plan. For scientific literature, OpenScholar combines passage retrieval, cited generation, and iterative self-feedback (Asai et al., 2026), while AutoSurvey retrieves papers, constructs an outline, and delegates subsection drafting to specialized LLMs (Wang et al., 2024b). These systems can synthesize reports but do not document the paper filtering process based on PRISMA 2020 (Page et al., 2021).

Systematic review tools. Some tools support individual review stages. ASReview prioritizes records for human screening through active learning from relevance judgments (van de Schoot et al., 2021); LGAR ranks abstracts zero-shot using graded, criterion-based LLM scores and dense reranking (Jaumann et al., 2025). RobotReviewer extracts trial characteristics and supports risk-of-bias assessment with sentences linked to the source document (Marshall et al., 2017).

Integrated workflows extend assistance across stages. AgentSLR pairs an epidemiological literature review workflow with stage-specific evaluation and describes an interface for expert verification of extracted values (Padarha et al., 2026). Its published workflow uses predefined eligibility criteria and domain-specific extraction schemas. We compare against it in Section 4. Ren et al. (2026) translate user criteria into screening rules and use multi-agent cross-review for clinical-trial screening. Their extraction workflow combines source-derived table standardization, iterative correction, and targeted human review. The commercial Elicit workflow proposes editable criteria and extraction fields and lets users return to earlier steps (Byun, 2025); it also provides evidence quotes, exclusion reasons, and PRISMA 2020 flow diagrams (Vardhaan and Mohanty, 2026). These workflows already combine stage automation, customization, evidence access, and human oversight.

To address these gaps, we develop ReviewPilot, a PRISMA-guided multi-agent system that coordinates literature search, screening, full-text retrieval, and information extraction. Researchers can tailor eligibility criteria and extraction schemas through dialogue, while agents generate screening guidance and per-field coding rules. Project memory retains configurations and corrections to support revision across stages (Sections 3.2 and 3.6). We evaluate the complete system on PERG and examine its workflows and screening agreement with human annotators in two case studies.

3 ReviewPilot Development

Refer to caption
Figure 2: ReviewPilot architecture and workflow. (1) The Lead Agent coordinates five review stages using project memory. Researchers configure stages and correct decisions or values. In the upper right, the Prompt Agent prepares screening guidance, an extraction schema, and coding rules without reviewer labels. (2) Screening returns a rationale and one of five likelihood levels. (3) Extraction returns values with verbatim excerpts. The label verified means the excerpt is found in the PDF text. Orange marks screening rationales and extraction evidence.

ReviewPilot is a conversational multi-agent system that covers five stages of a systematic literature review: search, screening, full-text retrieval, information extraction, and semantic categorization (Figure 2). Researchers can configure the review through dialogue or direct editing, inspect each stage’s outputs, and can override screening decisions or correct extracted values.

3.1 Architecture and Orchestration

A Lead Agent coordinates four specialized agents and two tools through action contracts (Appendix A.1). The Search Condition Agent designs the search strategy, and the Prompt Agent writes review-specific instructions (Section 3.2). The Screening Agent deduplicates and assesses records, and the Extraction Agent extracts structured information. The Literature Search Tool executes queries, and the PDF Download Tool retrieves full texts. The Lead Agent categorizes values itself.

The Lead Agent starts a stage only when its prerequisites are met and the outputs it depends on are current. It reports completion only after checking the expected artifacts and their required fields. Agent skills are structured Markdown instructions specifying procedures for search strategy, screening, prompt design, extraction, and categorization. A fixed mapping appends the matching skill to the LLM system prompts for these tasks (Appendix G).

3.2 Review-Specific Prompt Design

The Prompt Agent writes the review-specific parts of the screening and extraction instructions, following the prompt-design skill. After the eligibility criteria are confirmed, it writes screening guidance 𝒢 from the review objectives, criteria, search concepts, and up to 200 candidate records (titles and abstract openings). This guidance defines the review focus, domain terms, include and exclude categories, and tie-breaking rules. After screening, it drafts an extraction schema from the objectives, the requested fields, and the abstract openings of up to three included papers. Once the schema is confirmed, it writes the coding rules 𝒞 from up to 25 included papers, using their abstract openings and full-text sentences selected for each field.

The guidance and the coding rules are each drafted and then revised in a second LLM pass against the skill’s checklist (Madaan et al., 2023). Reviewer decisions and reference extraction values are not among the generation inputs. Researchers can edit the guidance, schema, and rules and must confirm each before the stage that uses it runs (Appendices G.3, G.4.1, and G.5.1).

3.3 Search & Screening

Search.

The Search Condition Agent identifies the concepts required for eligibility and proposes alternative terms for each concept. It builds a Boolean query by joining alternatives with OR and required concept groups with AND (Appendix A.2). Analytical dimensions that do not determine eligibility are omitted from the required groups. Researchers refine the concepts and query through dialogue or direct editing and review the sources, date range, and per-source limits. The Literature Search Tool then searches titles and abstracts in PubMed, arXiv, and OpenAlex. The saved query, settings, counts, and errors document the search as run.

Screening. After date filtering and deduplication (Appendix A.3), the model assesses each record pi, its title and available abstract, against the confirmed inclusion criteria ℐ, exclusion criteria ℰ, and screening guidance 𝒢:

(ri,ℓi)=fLLM​(pi,ℐ,ℰ,𝒢), (1)

where ri is a one-sentence rationale naming the deciding rule and ℓi is a qualitative likelihood label. Its five levels are definitely exclude, probably exclude, uncertain, probably include, and definitely include. The screening skill instructs the model to assess the study’s own work against the review focus and criteria, not topics mentioned only as background (Appendix G.4). Among these five levels, a record is excluded only when ℓi is probably exclude or definitely exclude. Records with the other labels are retained for full-text review. Records are also retained when the model call fails. The prompt requests the deciding rule and a verbatim title or abstract excerpt. An exclusion with an unmatched rule or unlocated excerpt is flagged for human review, but the record remains excluded.

3.4 Paper Retrieval & Information Extraction

Paper retrieval.

The PDF Download Tool tries a cascade of publisher, open-access, and preprint sources for each retained record. It checks PDF validity and compares opening-page text with the title. These heuristics do not guarantee retrieval success (Appendix A.4), so it generates a report to record the success or failure retrieval for each paper, and researchers can add missing PDFs manually.

Information extraction. The confirmed schema 𝒮={(fj,τj,δj)}j=1k defines each field by its name, type, and description (Appendix A.5). The coding rules 𝒞 specify how borderline values are coded. ReviewPilot places a full-text eligibility field first in the drafted schema, with options from the confirmed criteria. The model judges whether the paper remains eligible and names the criterion behind an exclusion. In a PDF assessment, an empty or unrecognized eligibility value does not exclude the paper. Excluded papers are omitted from categorization, and their exclusion reasons are recorded for PRISMA reporting.

For each available PDF, the Extraction Agent sends up to the first 400,000 characters of its text, with page markers, together with the schema and coding rules to the model (Appendix G.5). For each field, the prompt requests a value vj, verbatim excerpts, and page numbers. It requires an empty or null value when the supplied text neither states nor necessarily implies a value. Responses are checked for field presence, types, and value constraints. A failed check is recorded as an extraction failure for that paper. Passing these checks does not establish that the values are correct. ReviewPilot searches the normalized PDF text for the returned excerpts. A field with at least one located excerpt is marked verified, and the first located excerpt is stored with the page on which it was located. Otherwise, the field is unverified. Excerpt location establishes textual presence, not semantic support for the value or coverage of every value in a multi-value field.

For papers whose PDF was not retrieved, researchers can enable assessment from the abstract. When the selected model supports web search, it can seek web evidence for fields the abstract leaves open. Accepted values require located excerpts, and web pages must pass paper-identity checks. These outputs retain source labels and any source URLs without PDF page numbers and are reported separately from full-text assessments. Fields without evidence remain unavailable, and papers whose eligibility remains unavailable are not categorized.

3.5 Semantic Categorization

The Lead Agent categorizes extracted values only for papers retained after eligibility check. For a selected field, it proposes a set of categories with short descriptions (Appendices A.6 and G.6). The plan supports single-label or multiple-label assignment, and an Other category for values that do not fit. Researchers review and edit the plan before the Lead Agent assigns labels to each paper. Papers with no value for the field are marked unavailable.

3.6 Memory Design

Researchers work in a conversation panel and a stage-specific canvas. A chat request that changes criteria or the schema is saved as a draft, and confirmation is a canvas action (Appendices A.7 and H). Project memory stores the conversation history, current configurations, confirmed configuration snapshots, and each stage’s status and PRISMA counts.

In conversation, the Lead Agent receives its task instructions, the current request, the saved project state, and the conversation history. Its instructions give saved state precedence over superseded requests and distinguish drafts from confirmed configurations. Researchers reuse a previous project’s configuration by importing it as a draft that again requires confirmation. The system does not retrieve memories across projects automatically or learn preferences from corrections.

To override a screening decision, researchers select a confirmed criterion or guidance rule and give a reason. They also give reasons when correcting extracted values. Original decisions and values remain in review history. A change to a confirmed configuration or reviewed record marks affected downstream outputs as outdated until rerun.

4 Experiments & Results

We evaluate screening and structured information extraction separately against the expert annotations in PERG, a dataset released with AgentSLR (Padarha et al., 2026). Extraction uses the same expert-included papers for all methods, independently of each method’s screening predictions.

4.1 Experiment Setup

Data and reference annotations.

PERG is released under the CC BY 4.0 license. Its annotations originate from systematic reviews conducted by the Pathogen Epidemiology Review Group at Imperial College London for WHO priority pathogens (Cuomo-Dannenburg et al., 2024; Nash et al., 2024; Doohan et al., 2024; Morgenstern et al., 2025; McCain et al., 2025; Naidoo et al., 2026). Screening uses 5,614 title–abstract records for Lassa, Nipah, SARS, and Zika, with 854 expert inclusions (15.2%). All methods apply the five inclusion and six exclusion criteria specified in AgentSLR’s PERG template (Appendix B). All records are evaluated without date filtering or deduplication.

Extraction uses 178 annotated papers (79 for Ebola, 6 for Lassa, 36 for SARS, and 57 for Zika). We evaluate five fields: model type, stochastic or deterministic status, code availability, transmission routes, and interventions (Table B.2). PERG annotates each transmission model in a paper. Reference values are aggregated to the paper level by taking the union across models. Code availability is true if the paper reports available code for any model.

Models and evaluation metrics. We use gpt-6-luna through the OpenAI API,22 2 https://developers.openai.com/api/docs and DeepSeek V4.1 Flash and GLM-5.3-Flash through Together AI.33 3 https://docs.together.ai/intro The single-prompt LLM uses one instruction containing the screening criteria, or the study objective and field definitions for extraction. It retains uncertain screening cases and requests field-level excerpts for extraction, without ReviewPilot’s skills, coding rules, or schema validation (Appendix C).

We rerun AgentSLR using its public screening implementation and transmission-model extraction pipeline. Its prompts, parser, and internal full-text screening are preserved, as are the tool and provenance loops of its extraction stage. It reads the same PDF text as the other methods. We adapt AgentSLR’s API client and replace its original high reasoning setting (Table D.3). Extraction and gpt-6-luna screening use medium reasoning. Screening with the Together AI models uses provider defaults. Papers rejected by its internal screening remain in the evaluation with empty predictions.

ReviewPilot follows the screening and extraction procedures in Sections 3.3 and 3.4. It uses a fixed five-field extraction schema, with review-specific screening guidance and coding rules generated by the Prompt Agent. All methods receive the same papers and use the same reference annotations.

Prompt Agent uses the same model as its downstream stage. The agent receives the review objectives, criteria or field definitions, and samples of evaluation records or papers. Expert decisions and reference extraction values are excluded from the agent’s inputs. ReviewPilot’s screening procedure and prompt-design skill are refined using evaluation scores from these PERG pools. The pools are therefore not held out from method development.

We report one complete run per method and model. Decoding settings and output limits differ across methods and are recorded with each run (Appendix D). Transport errors and incomplete responses trigger retries. ReviewPilot also retries unparseable screening outputs. GLM-5.3-Flash exhausted its 65,536-token output limit on one paper. That paper is excluded from all three methods’ results on this model, leaving 177 papers. All table entries are single-run point estimates and do not characterize variation across repeated model runs.

Screening metrics. We pool the records and compute precision, recall, and F1 separately for the include and exclude classes. Each metric is then macro-averaged over the two classes. The review share, (TP+FP)/N, is the proportion of records retained for full-text review, where TP and FP denote retained expert-included and expert-excluded records, and N is the pool size. Macro recall averages recall for both classes and does not measure include-class recall alone.

Extraction metrics. Predicted and reference values are normalized with a fixed synonym mapping shared by all methods. At the paper–field level, matching values count as true positives, additional predicted values as false positives, and reference values absent from predictions as false negatives. Under AgentSLR’s empty-field convention, a field empty in both prediction and reference counts as one true positive. This convention applies to model type, stochastic or deterministic status, and code availability. For paper-level scoring, AgentSLR’s per-model predictions are aggregated identically to reference values. Its native model-matching evaluation is not used. Counts are pooled across papers and the five fields to compute precision, recall, and F1. AgentSLR’s additional fields are not scored.

The verified-correct rate is computed over paper–field pairs with a reference value. A pair counts as verified-correct when its complete normalized prediction matches the reference set and at least one returned excerpt is located in the paper. All methods use the same excerpt matcher. Excerpt location does not establish semantic support for the prediction (Gao et al., 2023) or coverage of every value in a multi-value field.

Cost estimation. We estimate API costs from returned token usage and the prices in Table D.1. Costs are reported in USD per 1,000 screened records or per extraction paper. Screening costs include ReviewPilot’s guidance generation, whereas extraction costs exclude coding-rule generation.

4.2 Screening Results

Table 1: Screening results pooled over four PERG pathogens (5,614 records with 854 expert inclusions). Precision, recall, and F1 are macro-averaged over the include and exclude classes. Review share is the proportion of records retained for full-text review. Cost is USD per 1,000 records. Bold marks the best value within each model (highest for ↑, lowest for ↓).

ReviewPilot has the highest screening macro precision, recall, and F1 on each model in Table 1. Its macro F1 exceeds AgentSLR’s by 5.3–10.3 points and the single-prompt LLM’s by 7.0–19.0 points. ReviewPilot retains 26–29% of records, versus 33–42% for AgentSLR and 35–54% for the single-prompt LLM. The lower share describes the number of records sent to full-text review. It does not establish that fewer expert inclusions are missed or that human review time decreased. ReviewPilot’s reported API cost is lower than AgentSLR’s on each model, while the single-prompt LLM has the lowest reported API cost.

4.3 Extraction Results

Table 2: Extraction results on PERG (178 papers, or 177 for GLM-5.3-Flash after excluding the same paper for all methods). Precision, recall, and F1 are computed from counts pooled across papers and the five fields. Verified-correct rate requires the complete normalized prediction to match the reference set and at least one excerpt to be located in the paper. Cost is USD per paper, excluding coding-rule generation. Bold marks the best value (highest for ↑, lowest for ↓).

ReviewPilot has the highest pooled precision, recall, and F1 on each model in Table 2. Its F1 exceeds AgentSLR’s by 3.7–4.7 points and the single-prompt LLM’s by 1.5–1.7 points. ReviewPilot’s verified-correct rate reaches 0.703–0.714, compared with 0.405–0.449 for AgentSLR and 0.528–0.561 for the single-prompt LLM. More paper–field pairs therefore combine a complete normalized match to the reference set with at least one excerpt located in the paper. Semantic verification is still required to assess whether the excerpts support the predicted values. ReviewPilot’s reported extraction cost is lower than AgentSLR’s and higher than the single-prompt LLM’s on each model. Appendix E gives the screening results by pathogen and extraction results by field.

5 Case Studies

We apply ReviewPilot to reviews of LLM applications in biomedicine and human–computer interaction (HCI).

5.1 Complete Review Workflows

Both projects used gpt-6-luna and searched PubMed, arXiv, and OpenAlex, taking up to 1,000 results per source. Searches covered publications dated 1 January 2023 to 1 October 2026. Figure 3 and Figure F.1 in Appendix F.4 trace the workflows, outputs, and actions.

Refer to caption
Figure 3: HCI workflow in PRISMA 2020 format (Page et al., 2021). Squares track records. Green denotes retention, pink exclusion, grey removal or non-retrieval. Outlines identify numbered examples. Included squares show the first assigned category in right-panel order. Counts include all assignments. The right panel shows agents, tools, outputs, researcher actions, system processing times, and LLM costs of completed-workflow calls.
HCI.

The 2,241 records yielded 752 categorized studies (Figure 3); 153 reports were not retrieved, and full-text assessment excluded 75 of 827 reports. The researcher reinstated three excluded records, including a system evaluation of an interactive tool. The examples contrast this reversal with a rapid-review exclusion and pair GPT-4 and 43 participants with source excerpts. Before categorization, the researcher regrouped the proposed application categories. Studies could receive multiple labels.

Biomedicine.

The 3,000 records yielded 1,341 categorized studies (Figure F.1). Screening retained 1,705 records, including four exam evaluations reinstated by the researcher. Of these, 336 reports were not retrieved and seven not extracted. Full-text assessment excluded 21 of 1,362 reports. The examples show a survey exclusion, a reinstated exam evaluation, and extraction of GPT-4o and expert evaluation from a radiology study. The researcher kept the five proposed task categories. ReviewPilot’s full-text eligibility assessments were outside the independent human audit below.

5.2 Human Agreement and Inspection

Screening.

For each topic, two annotators from our research team with expertise in HCI or biomedicine independently labeled titles and abstracts without seeing ReviewPilot’s output (criteria in Appendix F). Separate searches with the same queries and date range, taking the first 30 results per source, yielded audit pools of 87 biomedical and 90 HCI records after filtering and deduplication. ReviewPilot screened each pool in a separate run with gpt-6-luna. Its κ against each annotator exceeded inter-annotator agreement in biomedicine and, in HCI, fell on either side of it (Table F.1).

Extraction inspection.

Source checks in the complete workflows corrected three field values per topic (Table F.2). HCI corrections restored participant counts and distinguished human experiments from assessments of agents. Biomedical corrections removed unsupported task, data-source, or adaptation labels. Missing excerpts were added. The selected inspections provide qualitative error analysis. Appendix F gives sampling and schemas.

6 Discussion and Conclusion

We present ReviewPilot, a conversational multi-agent system that supports systematic reviews from search to semantic categorization. Researchers confirm criteria and schemas, a Prompt Agent writes review-specific guidance and coding rules for applying them, and a project memory retains configurations and corrections. Across three LLMs, ReviewPilot achieves higher screening macro F1, pooled extraction F1, and verified-correct rates on PERG than a single-prompt LLM and AgentSLR.

These gains should be read with care. PERG pools also inform ReviewPilot’s development, so the results do not establish performance on unseen reviews. A located excerpt shows that the quoted text appears in the paper, but whether it supports a decision or value still requires human judgment.

The case studies show why memory design matters. When researchers check flagged and sampled outputs, they reverse some screening exclusions and correct some field values, and the system keeps each change with its reason. ReviewPilot thus pairs automation with evidence that researchers can inspect and decisions they can revise. Future work should measure how these features affect review effort and decision quality, and extend the evaluation to reviews with other evidence types.

Limitations

Broad validation across reviews, evidence types, and review teams remains incomplete. ReviewPilot’s screening procedure and prompt-design skill are refined using scores from the same PERG pools used for evaluation, so the reported gains do not establish performance on unseen reviews. Expert decisions and reference values are excluded from the Prompt Agent’s inputs. Quantitative extraction covers five fields from epidemiological transmission models. The case-study screening audits use small, non-random pools labeled by our research team, and the selected extraction inspections provide qualitative error analysis. Full-text eligibility decisions are not independently audited. We report one run per method and model without confidence intervals. These estimates do not characterize variation across repeated runs. Macro-averaged screening metrics do not isolate include-class sensitivity, which matters for avoiding missed studies (Cohen et al., 2006; O’Mara-Eves et al., 2015). AgentSLR’s original high reasoning setting is replaced with medium reasoning or provider defaults. Excerpt verification establishes textual presence, but does not assess semantic support or whether excerpts cover every value in a multi-value field (Gao et al., 2023).

Search coverage is limited to PubMed, arXiv, and OpenAlex and constrained by the query and per-source result limits. Full-text extraction depends on successful PDF retrieval. Researchers can add PDFs manually, but the reported workflows do not separately quantify retrieval outcomes by publication access status. The contribution of subscription barriers to unretrieved reports therefore remains unquantified in the reported results. Access constraints may affect which studies enter extraction and categorization. Assessments based on abstracts or web sources are not separately validated. These sources may lack the evidence needed to populate every field.

Future evaluations should use reviews held out from method development, cover further evidence types and extraction schemas, and independently audit full-text eligibility and semantic support for extracted values. Repeated runs should report uncertainty and include-class recall. Prospective studies with review teams are needed to assess reviewer effort and decision quality. Retrieval evaluations should report outcomes by access status and assess how manual PDF submission and fallback assessment affect evidence coverage.

ReviewPilot also relies on hosted models whose behavior may change across versions (Chen et al., 2024). Its outputs require human verification, and the system is intended to support the independent review procedures recommended by Cochrane (Higgins et al., 2023).

References

Appendix Contents

Appendix A ReviewPilot Implementation Details

This appendix gives the implementation details behind Section 3, in the order of the main text.

A.1 System and Orchestration

The system uses a Starlette backend and a JavaScript interface. A project-level setting selects the model used for search setup, conversation, screening, and extraction. Each action contract specifies a component’s inputs and expected outputs. Before reporting a stage as complete, the Lead Agent checks that the stage’s expected artifacts exist and contain their required fields. Each skill is stored as a SKILL.md file in the Agent Skills format (Zhang et al., 2025). A fixed mapping assigns the skills to the LLM tasks named in Section 3.1 and appends the selected skill to the task’s system prompt.

A.2 Search

For a research description d, the Search Condition Agent forms the Boolean query

𝒬⁡(d)=⋀g∈𝒢req​(d)(⋁t∈𝒯g​(d)t), (2)

where 𝒢req​(d) is the set of required eligibility groups and 𝒯g​(d) contains the alternative terms of group g. Wang et al. (2023) evaluate Boolean queries of this form written by ChatGPT for systematic review searches. The Literature Search Tool applies source-specific syntax for PubMed, arXiv, and OpenAlex (Priem et al., 2022) to the query while preserving its Boolean grouping, and it records the executed query, settings, counts, and errors separately for each source.

A.3 Screening Preprocessing

The Screening Agent first filters records by publication date. Records with missing dates, or with date intervals that overlap the search range, are retained. It then removes exact and near duplicates. Exact matching normalizes title case, punctuation, and whitespace. Near-duplicate detection compares title and author signatures with term frequency–inverse document frequency (TF-IDF) cosine similarity, computed with scikit-learn (Pedregosa et al., 2011), at a default threshold of 0.70. Records with distinct nonempty DOIs or PubMed identifiers are kept separate. Each removal is recorded with the relevant reason.

A.4 Full-Text Retrieval

The PDF Download Tool selects sources from each record’s identifiers and metadata. Routes include direct links, publisher pages, DOI resolution, PubMed Central, Europe PMC, Unpaywall, arXiv, bioRxiv, and medRxiv, with request throttling, retries, and a browser fallback that can be disabled. The identity check compares the text of the PDF’s opening page with the expected title.

A.5 Extraction

In the schema 𝒮, fj, τj, and δj denote a field’s name, JSON-compatible type, and description. Fields may also have value constraints. The Extraction Agent reads the PDF text with pypdf and inserts a page marker before the text of each page. The schema checks cover field presence, declared types, and value constraints. Proposed excerpts are matched against normalized PDF text, and a located excerpt is recorded with the page on which it is found.

A.6 Categorization

For a selected field fj with nonempty extracted values 𝒱j, the Lead Agent proposes the category plan 𝒦j=fLLM​(fj,sample⁡(𝒱j),m), where sample⁡(𝒱j) takes the first 150 distinct values in record order, each shortened to 300 characters, and m selects single-label or multiple-label assignment. It has at most five categories, fewer when the field has few distinct values, and includes an Other category within that limit when some values fit none. Returned labels are normalized when they match approved names. Multiple-label responses containing other labels are rejected. Papers with no value for the field are marked as unavailable. Saved outputs keep the field, mode, category descriptions, and per-paper assignments.

A.7 Interface, Memory, and Revision

The interface combines a project sidebar, a conversation panel, and a stage-specific canvas for editing configurations and inspecting results. For example, the chat request add a field for sample size edits the schema draft. Researchers can run screening or extraction on samples of one to five papers, kept separate from full-run outputs. In conversation, the Lead Agent’s context is 𝒫chat=𝒫task⊕𝒮project⊕ℋproject, which concatenates task instructions and the current request with the saved project state and the conversation history. Configurations that can be imported from a previous project are its search setup, criteria, schema, and category plan. Edits submitted against an older project revision are rejected.

Appendix B PERG Data, Criteria, and Extraction Fields

Table B.1 gives the PERG records and papers used in Section 4. Table B.2 describes the five evaluated extraction fields.

Table B.1: PERG data used in §4. Incl.: expert title/abstract inclusions.
Screening criteria.

AgentSLR’s screening template states the PERG criteria, and all three methods use these 11 rules: AgentSLR runs its published template unchanged, and ReviewPilot and the single-prompt baseline receive the same rules as an inclusion list and an exclusion list. There are five inclusion criteria: (1) the target pathogen; (2) English; (3) peer-reviewed original research, with systematic reviews and meta-analyses given special consideration; (4) human subjects, or animal studies that report transmission or vector parameters; and (5) at least one of ten content types (outbreak details, a transmission model, transmission, timing, severity or genetic parameters, overdispersion, seroprevalence, risk factors, or vector parameters). There are six exclusion criteria: (1) another pathogen; (2) non-English; (3) conference abstracts, posters, or correspondence; (4) in-vitro work only; (5) animal-only studies without transmission parameters; and (6) laboratory outbreaks.

Table B.2: The five PERG extraction fields evaluated in §4.3. A paper’s gold value is the set of values over all its models. The transmission_route and interventions_type fields often take several values.

Appendix C Baselines

The single-prompt LLM sends one request per record or paper. Earlier evaluations of LLM screening (Guo et al., 2024a; Wang et al., 2024a; Khraisha et al., 2024) and data extraction (Gartlehner et al., 2024; Khraisha et al., 2024) also prompt the model directly; Lieberum et al. (2025) and Scherbakov et al. (2025) review this work. It receives the same records, papers, eligibility rules and extraction schema as ReviewPilot, but no skill, review-specific guidance, coding rules or schema validation. Its prompts are reproduced verbatim below. Shaded text marks slots. For screening, the criteria slots hold the published AgentSLR rules (Appendix B). AgentSLR runs the published screening template unchanged. Table D.3 lists every change made to its public implementation.

Appendix D Run Configuration

Table D.1 lists the models and the prices used for cost estimates, and Table D.3 the request settings of each method.

Table D.1: Models and prices (USD per million tokens). The Together AI identifiers are deepseek-ai/DeepSeek-V4.1-Flash and zai-org/GLM-5.3-Flash. Reasoning tokens are billed as output.
Table D.2: Changes made to AgentSLR’s public implementation for §4.
Table D.3: Request settings of each method. Output caps are in tokens and include reasoning. Transport errors and empty or truncated outputs are re-sent with the identical request, and valid outputs are never resampled. ReviewPilot screening also re-sent unparseable outputs. All methods read the same PDF text (first 400,000 characters).

Appendix E Additional Results

Tables E.2 and E.2 break down Tables 1 and 2 by pathogen and by field, with the same metrics. All numbers come from the runs in Tables 1 and 2. No model is called again.

Table E.1: Screening results per pathogen. Precision, recall, and F1 are macro-averaged over the include and exclude classes, as in Table 1. Bold marks the best value within each model.
Table E.2: Extraction results per field (177 papers for GLM-5.3-Flash), counted as in Table 2. Bold marks the best value within each model.

Appendix F Case-Study Details

Refer to caption
Figure F.1: Biomedical review workflow in the PRISMA 2020 format (Page et al., 2021). The layout and record colors follow Figure 3. The 3,000 records yield 1,341 included studies after screening and full-text assessment; 336 reports are not retrieved and seven are retrieved but not extracted, shown in dark grey within the not-retrieved box. Numbered examples show a survey exclusion (1), a reversed exclusion of a medical-exam evaluation (2), and extraction of model names and expert evaluation with source excerpts (3). Category counts include every assignment to a study. System processing times and LLM costs of completed-workflow calls are shown beside each stage.
Table F.1: Screening agreement (Cohen’s κ; Cohen, 1960) in separate audit-pool evaluations (87 biomedical and 90 HCI records). A and B are the independent annotators. Shared-label agreement uses only the 81 biomedical and 78 HCI records on which the annotators agree, with one and six ReviewPilot disagreements, respectively.
Table F.2: Researcher inspections in the complete workflows. Flagged records and stratified paper samples are selected for checking. These counts do not estimate corpus-level error rates.
Table F.3: Eligibility criteria for the case-study screening audits and both complete workflows (Section 5).
Table F.4: Case-study extraction schema, with five substantive fields per topic. List fields may contain multiple values. Unreported information is left empty, without inference or default values. Categorical list fields use the listed labels and Other for values outside them. Model names are free text.

Figure F.1 shows the biomedical workflow corresponding to the HCI workflow in Figure 3. Tables F.1 and F.2 report screening agreement and researcher inspections, respectively. Tables F.3 and F.4 specify the eligibility criteria and extraction schemas. Both complete workflows assessed full-text eligibility under the screening criteria. The independent annotators did not assess full-text eligibility.

Extraction inspections.

HCI sampling covered papers with participant counts, technical evaluations without users, Other application areas, and fine-tuning or RAG. A consistency check selected papers with user-facing methods and missing participant counts. The HCI coding rules included human output evaluators in participant counts and counted participants shared across studies only once. Corrections included restoring reported counts and distinguishing human experiments from evaluations of agents. Biomedical sampling covered expert evaluation, clinical notes, and other tasks. Corrections removed labels based on incidental mentions: tool use for output formatting, benchmark questions absent from the evaluated data, and patient communication outside the actual task. These checks examined values against full-text evidence and added missing excerpts.

Appendix G ReviewPilot Prompts

This appendix lists every prompt that ReviewPilot’s agents send to the LLM (§3, §4). Following the order in Figure 2, it covers the Lead Agent’s chat prompts, the Search Condition Agent, the Prompt Agent, the Screening Agent with the PERG screening guidance, the Extraction Agent with the PERG coding rules, and the Lead Agent’s categorization prompts. The Literature Search Tool and the PDF Download Tool make no LLM calls. A skill is appended to its agent’s system prompt inside a <reviewpilot-agent-skill> block. Shaded text marks slots filled for each review or record. The prompt text is reproduced verbatim. The colours, the labels on the left of each box and the check and cross marks are added for reading.

G.1 Lead Agent

The Lead Agent answers questions about the project in chat and turns the researcher’s chat requests into edits of the screening criteria and of the extraction schema, which are saved as drafts for the researcher to confirm. These prompts carry no skill. The Lead Agent’s categorization prompts are in Appendix G.6.

G.2 Search Condition Agent

The Search Condition Agent writes the concept strategy from the research request and revises it when the researcher asks in chat. The initial prompt is shown as it is sent when a project starts from a chat request, where the request may also set sources, record limits and dates. A response that fails validation is retried once with the reason appended. The Prompt Agent uses the same retry.

G.3 Prompt Agent

The Prompt Agent writes the screening guidance, the extraction schema and the coding rules. The screening guidance and the coding rules each take two calls, first to draft and then to review the draft against the skill’s checklist.

G.4 Screening Agent

The system prompt is an opening sentence followed by the screening skill.

G.4.1 PERG Review Focus and Domain Rules

The Prompt Agent wrote these for each pathogen from the review objectives, the confirmed criteria and the candidate titles and abstracts, without reviewer labels. They are inserted into the screening prompt before the inclusion criteria. These are the gpt-6-luna versions. For DeepSeek V4.1 Flash and GLM-5.3-Flash, the Prompt Agent writes its own guidance using each model.

G.5 Extraction Agent

The system prompt is an opening sentence followed by the evidence instruction and the extraction skill. The user prompt carries the research scope, the finalized schema, the task instruction, the coding rules and the paper text. For a paper without full text, the abstract step appends a note to the system prompt and sends the title and abstract in place of the paper text. The web step then asks for the fields that are still empty.

G.5.1 PERG Coding Rules

The Prompt Agent wrote these for each pathogen from the review objectives, the confirmed schema and the included papers (abstracts and the full-text sentences that speak to each field), without gold values. They are inserted into the extraction prompt before the paper text, using the rules for the paper’s pathogen. These are the gpt-6-luna versions. For DeepSeek V4.1 Flash and GLM-5.3-Flash, the Prompt Agent writes its own coding rules using each model.

G.6 Categorization

The Lead Agent categorizes the extracted values itself, with the Categorization Skill appended to each system prompt. One call plans the categories from every paper’s value of the selected field. One call per paper then assigns it to one category or to several.

Appendix H System Interface

Figures H.2–H.8 show ReviewPilot at each stage of the biomedical review in Figure F.1. Each screen has the project sidebar, the stage canvas under the five-step progress bar, and the conversation with the Lead Agent. The screenshots are taken from the finished project, and nothing on the screen is edited. Activity cards in the conversation record each stage as it finished, so the screening card reports the totals from before the researcher reinstated four records (1,701 included and 1,014 excluded), while the canvas and the PRISMA flow show the final counts. Full-Text Retrieval and Information Extraction are marked as partial because 336 papers had no PDF and seven are not extracted.

Refer to caption

Figure H.1: Search Setup. In the conversation, the researcher describes the topic and asks to merge two concepts and to set the date range and per-source limits. The canvas shows the resulting research question, the two required concepts, the Boolean query, the three sources with 1,000 results each, and the date range.

Refer to caption

Figure H.2: Paper Screening displays the finalized inclusion and exclusion criteria and the review guidance that the Prompt Agent drafted from them and 200 collected records, confirmed by the researcher before screening.

Refer to caption
(a)
Refer to caption
(b)

Figure H.3: Reviewing screening decisions. (a) The review dialog for one of the four exam-evaluation studies that the researcher reinstated (example 2 in Figure F.1), with the saved decision, the researcher’s rationale and approved criterion, and the controls for changing a decision. (b) Two rows of the screening list: a model decision with its likelihood label, rationale, decisive rule, and a quote verified in the title or abstract, and a reinstated record marked as human reviewed.

Refer to caption

Figure H.4: Full-Text Retrieval. PDFs are retrieved for 1,369 of 1,705 records. Each of the 336 failures is listed with its reason and can be retried or supplied manually.

Refer to caption

Figure H.5: Information Extraction displays the confirmed coding rules (drafted by the Prompt Agent from the finalized schema and the full text of 25 included papers), the notice on the 336 papers without full text, and the first two fields of the six-field schema.

Refer to caption

Figure H.6: Inspecting an extracted value of the radiology study in Figure F.1 (example 3). The excerpt supporting llm_models = GPT-4o is located verbatim on page 3 of the PDF and shown beside the page text. The researcher can correct the value with a supporting quote and a reason.

Refer to caption
(a)
Refer to caption
(b)

Figure H.7: Categorization & Analysis. (a) The top of the stage shows 1,341 papers in five categories and the upper part of the PRISMA 2020 flow. (b) Category counts for the biomedical task field. A study can belong to several categories.

Refer to caption

Figure H.8: The PRISMA 2020 flow that ReviewPilot generates for the run, from 3,000 identified records to 1,341 included and categorized studies, with exclusion counts by reason.

注意转载授权 · 阅读原文

来源:arXiv 关键词查询 · AI 科学家/同行评审/文献 · arxiv.org

引用原文

Zhaoqian Xue. ReviewPilot: A Multi-Agent System for Screening and Data Extraction in Systematic Reviews[EB/OL]. (2026-10-15)[访问日期]. https://arxiv.org/abs/2610.21042v1.