Papers › Pi-GPS: Enhancing Geometry Problem Solving by Unleashing the Power of Diagrammatic Information

Pi-GPS: Enhancing Geometry Problem Solving by Unleashing the Power of Diagrammatic Information

7 Mar 2025arXiv:2503.05543archive 2025-07-28

Junbo Zhao, Ting Zhang, Jiayu Sun, Mi Tian, Hua Huang

Geometry problem solving has garnered increasing attention due to its potential applications in intelligent education field. Inspired by the observation that text often introduces ambiguities that diagrams can clarify, this paper presents Pi-GPS, a novel framework that unleashes the power of diagrammatic information to resolve textual ambiguities, an aspect largely overlooked in prior research. Specifically, we design a micro module comprising a rectifier and verifier: the rectifier employs MLLMs to disambiguate text based on the diagrammatic context, while the verifier ensures the rectified output adherence to geometric rules, mitigating model hallucinations. Additionally, we explore the impact of LLMs in theorem predictor based on the disambiguated formal language. Empirical results demonstrate that Pi-GPS surpasses state-of-the-art models, achieving a nearly 10% improvement on Geometry3K over prior neural-symbolic approaches. We hope this work highlights the significance of resolving textual ambiguity in multimodal mathematical reasoning, a crucial factor limiting performance.

PaperPDFCode Syntology ranMethod as code

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 7 code samples harvested from 1 repository linked to this paper: 7 ran (of which 1 constructed an object rather than computing a result; 5 with no instrument failure: 1 honoured, 3 violated, 1 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: found in paper text by Syntology: 7 samples from 1 repository, 7 ran (5 with no instrument failure; 2 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-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

hellozting/Pi-GPS found in paper text by SyntologySyntology: 7 samples, 7 ran (2 instrument-failed) · 0 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

7 samples harvested: 7 ran (of which 1 constructed an object rather than computing a result; 5 with no instrument failure: 1 honoured, 3 violated, 1 with no contract checked; 2 where Syntology's instrument failed) · 0 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.

1ran · honoured contract
3ran · violated contract
2ran · our draft was wrong
1ran

Licence: 7 of the 7 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 hellozting/Pi-GPS. “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.

hellozting/Pi-GPS found in paper text by Syntology 7 samples, 7 ran (2 instrument-failed) · 0 unverified
LogicSolver Solver/logic_solver.py ran no licence file found · pointer only · 56a1d877006b358a · report fixture: returned LogicSolver · level recorded 2026-09-22
angle_area_formula Solver/logic_solver.py ran · our draft was wrong no licence file found · pointer only · de9957623fbf197a · report fixture: signature a:int/0/int, b:int/0/int, angle:int/0/int · returned Mul · level recorded 2026-09-22
hasNumber Solver/logic_solver.py ran · violated contract fingerprinted no licence file found · pointer only · 17a6df8f16c6b529 · report fixture: signature lst:list/1/str · returned bool · level recorded 2026-09-22
heron_triangle_formula Solver/logic_solver.py ran · honoured contract fingerprinted no licence file found · pointer only · e6f4a42d81e688ba · report fixture: signature a:float/0/float, b:float/0/float, c:float/0/float · returned float · level recorded 2026-09-22
isAlgebra Solver/logic_solver.py ran · violated contract no licence file found · pointer only · 722011153b6800a8 · report fixture: signature number:Add/0/? · returned bool · level recorded 2026-09-22
isNumber Solver/logic_solver.py ran · violated contract no licence file found · pointer only · 7134b436156bc5e1 · report fixture: signature number:str/0/str · returned bool · level recorded 2026-09-22
sort_points Solver/logic_solver.py ran · our draft was wrong fingerprinted no licence file found · pointer only · c07bed8f4e04921d · report fixture: signature points:list/1/int · returned list · level recorded 2026-09-22

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for Pi-GPS (graph method: Pi-GPS). 7 bricks; individually on a fixture: 7 ran (of which 1 constructed an object rather than computing a result; 5 with no instrument failure: 1 honoured, 3 violated, 1 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified. The assembly has not been run end-to-end.

  1. LogicSolver entry · level 1 · ran · 56a1d877006b358a
  2. angle_area_formula helper · level 1 · ran · our draft was wrong · de9957623fbf197a
  3. hasNumber helper · level 1 · ran · violated contract · 17a6df8f16c6b529
  4. heron_triangle_formula helper · level 1 · ran · honoured contract · e6f4a42d81e688ba
  5. isAlgebra helper · level 1 · ran · violated contract · 722011153b6800a8
  6. isNumber helper · level 1 · ran · violated contract · 7134b436156bc5e1
  7. sort_points helper · level 1 · ran · our draft was wrong · c07bed8f4e04921d

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2503.05543") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Geometry Problem SolvingMathematical Reasoning

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

AttentionSoftmax

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