Many scientific agents built on large language models run a common loop - they retrieve evidence, build a record of what they have found, judge whether that record is sufficient for the task, and, if not, use the record to direct the next retrieval. Each round's record is the next round's input, so the process is recursive. We call it recursive knowledge construction.
Two design axes decide how well this works, and both are usually assumed rather than measured, because such agents are evaluated only end to end:
- What the recursion builds: the evidence state.
- What controls it: the judge that decides when to stop.
ProClaim is a minimal instrument that makes both axes explicit, so each can be varied with the other held fixed. It exercises the recursive knowledge construction loop in consensus claim verification: establishing a claim's stance from the open literature rather than from a single given passage. ProClaim-eval (datasets/) provides 718 such claims with SUPPORT / REFUTE gold labels from five expert-curated databases.
Supplementary code and data for the submission. ProClaim is a sufficiency-aware agentic verifier for open-domain scientific claim verification. It determines a claim's consensual stance from the existing literature through iterative evidence construction.
datasets/: ProClaim-eval, five claim subsets (SIGNOR, ConnectomeDB, ExTRI, NUBASE, NASA Exoplanet Archive), 718 claims, packed in the password-protecteddatasets/proclaim_eval.zip. See datasets/README.md.src/proclaim/: the ProClaim verifier (evidence state, paper search, fact extraction, sufficiency judge).experiments/: evaluation entry points, baselines and the YAML config of every reported run. See experiments/README.md.scripts/sufficiency_classifier/: training data generation, feature extraction and training of the sufficiency judge, including the τ ablation.results/ablation/models/tau_0.50_seed_42/: weights of the trained sufficiency judge.
All commands run from the repository root.
-
Set up the environments (installs
uvif needed, runsuv sync, creates.envfrom.env.example, builds the.venv310NER environment used by the feature pipeline, and unpacks the dataset CSVs intodatasets/;bash scripts/unpack_datasets.shunpacks them alone):bash scripts/setup_proclaim.sh
-
Add
ANTHROPIC_API_KEYto.env. The example config uses hosted Claude models only and needs no local model endpoint. -
Verify one claim:
bash scripts/run_claim_example.sh --claim "GNAS directly activates ADCY1."This uses
experiments/configs/smoke_config.yamland writes the notebook, logs and evidence state underresults/claim_example/.--configand--output-dirselect another config or output folder.
See .env.example. The paper's runs use Claude Sonnet 4.6 as the outer agent (Anthropic API or
Vertex AI) and a local Qwen3.5-9B served by vLLM at LLM_BASE_URL for the extraction subagent.
datasets/ ProClaim-eval archive (CSVs and the 40-claim samples)
src/proclaim/ Verifier, retrieval and sufficiency logic
experiments/ Evaluation runners, baselines, configs
scripts/ Setup, single-claim example, sufficiency-judge training
results/ Trained sufficiency-judge weights
figs/ README figures

