Papers › Self-Guiding Exploration for Combinatorial Problems

Self-Guiding Exploration for Combinatorial Problems

28 May 2024arXiv:2405.17950archive 2025-07-28

Zangir Iklassov, Yali Du, Farkhad Akimov, Martin Takac

Large Language Models (LLMs) have become pivotal in addressing reasoning tasks across diverse domains, including arithmetic, commonsense, and symbolic reasoning. They utilize prompting techniques such as Exploration-of-Thought, Decomposition, and Refinement to effectively navigate and solve intricate tasks. Despite these advancements, the application of LLMs to Combinatorial Problems (CPs), known for their NP-hardness and critical roles in logistics and resource management remains underexplored. To address this gap, we introduce a novel prompting strategy: Self-Guiding Exploration (SGE), designed to enhance the performance of solving CPs. SGE operates autonomously, generating multiple thought trajectories for each CP task. It then breaks these trajectories down into actionable subtasks, executes them sequentially, and refines the results to ensure optimal outcomes. We present our research as the first to apply LLMs to a broad range of CPs and demonstrate that SGE outperforms existing prompting strategies by over 27.84% in CP optimization performance. Additionally, SGE achieves a 2.46% higher accuracy over the best existing results in other reasoning tasks (arithmetic, commonsense, and symbolic).

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

By repository: official repository: 11 samples from 1 repository, 8 ran (4 with no instrument failure; 4 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-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

zangir/llm-for-cp officialmentioned in papermentioned on GitHubSyntology: 11 samples, 8 ran (4 instrument-failed) · 3 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

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

1ran · honoured contract
3ran · our draft was wrong
1ran; the contract check could not run
3ran
3unverified

Licence: 11 of the 11 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 zangir/llm-for-cp. “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”. For 1 sample that ran, the graph records a signature this page does not show: an argument's recorded type or element kind is a printout of an object in Syntology's harness (such as a mock object, a class or a pandas printout), not the type of an input, so it does not describe the call's shape. “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.

zangir/llm-for-cp official repository 11 samples, 8 ran (4 instrument-failed) · 3 unverified
compute_cost_vrp solver.py ran; the contract check could not run (RAISES) no licence file found · pointer only · d6f8f6a98205bc59 · report fixture: signature solution:list/1/int, dist_mat:ndarray/2/float · returned float32 · level recorded 2026-09-24
create_data_model solver.py ran · our draft was wrong no licence file found · pointer only · 8bf59f21910e4299 · report fixture: signature dist_mat:ndarray/2/int, num_vehicles:int/0/int · returned dict · level recorded 2026-09-24
fast_SGE method.py ran no licence file found · pointer only · 35d66cefbae359af · report fixture: signature Q:str/0/str, f:MockPredictor/0/? · returned str · level recorded 2026-09-24
get_gap data_processing.py ran fingerprinted no licence file found · pointer only · 00610d35deeae7fa · report fixture: signature cost:float/0/float, optimal_cost:float/0/float · returned float · level recorded 2026-09-24
get_graph_mat solver.py ran · our draft was wrong no licence file found · pointer only · e488156d387beeea · report fixture: signature n:int/0/int, size:int/0/int · returned tuple · level recorded 2026-09-24
numeric_answer_extractor data_processing.py ran · honoured contract fingerprinted no licence file found · pointer only · bd32bbccb8f223ec · report fixture: signature text:str/0/str · returned int · level recorded 2026-09-24
predict_openai_model models.py ran no licence file found · pointer only · b397a5eb28c8b6d0 · report fixture: returned str · level recorded 2026-09-24
separate_lines method.py ran · our draft was wrong fingerprinted no licence file found · pointer only · 11355bef5c20756b · report fixture: signature text:str/0/str · returned list · level recorded 2026-09-24
SGE method.py unverified no licence file found · pointer only · ffb105b8b339cd3a · report
get_huggingface_dataset data_processing.py unverified no licence file found · pointer only · bc6819812bf5fee8 · report
predict_openai_ci_model models.py unverified no licence file found · pointer only · 7f5b1f663af490df · report

Tasks

ManagementNavigate

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