Primary evidence
- LeanConjecturer: Automatic Generation of Mathematical Conjectures for Theorem ProvingS1 · Primary research · Paper · 2025-06-27
- LeanConjecturer generation and evaluation repositoryS1 · Primary research · Repository
The pipeline extracts definitions and theorem context from Lean files, asks an LLM to propose new formal statements, checks generated statements through Lean and separates harder candidates for subsequent training.
The LeanConjecturer paper reported generating 12,289 university-level Lean conjectures from 40 Mathlib seed files, of which 3,776 were syntactically valid and not discharged by the chosen `aesop` non-triviality filter, and showed that such generated problems could support domain-specific reinforcement learning for theorem proving.
The pipeline extracts definitions and theorem context from Lean files, asks an LLM to propose new formal statements, checks generated statements through Lean and separates harder candidates for subsequent training. The paper also reports several non-trivial topology examples as evidence that the pipeline can produce mathematically useful statements rather than only superficial perturbations.
Formal theorem provers depend heavily on available theorem statements and training tasks. LeanConjecturer supplied a reproducible route for expanding that problem distribution from the formal library itself and linked conjecture generation directly to reinforcement-learning data creation.
Significance rationale: LeanConjecturer made conjecture generation a scalable formal-mathematics pipeline rather than an occasional by-product of theorem proving, combining Mathlib context extraction, LLM generation and Lean-based filtering to create large numbers of candidate training problems.
—
The arXiv research record introduced LeanConjecturer and reported the generated-conjecture counts, filtering procedure and theorem-proving training results.
The public LeanConjecturer repository exposes the generation and evaluation pipeline. The generated data directory is not committed in the repository, so E3 records inspectable implementation rather than independent verification of the paper's novelty claims or every generated theorem.
No corrections recorded.