Papers › Extracting Interpretable Logic Rules from Graph Neural Networks

Extracting Interpretable Logic Rules from Graph Neural Networks

25 Mar 2025arXiv:2503.19476archive 2025-07-28

Chuqin Geng, Zhaoyue Wang, Ziyu Zhao, Haolin Ye, Xujie Si

Graph neural networks (GNNs) operate over both input feature spaces and combinatorial graph structures, making it challenging to understand the rationale behind their predictions. As GNNs gain widespread popularity and demonstrate success across various domains, such as drug discovery, studying their interpretability has become a critical task. To address this, many explainability methods have been proposed, with recent efforts shifting from instance-specific explanations to global concept-based explainability. However, these approaches face several limitations, such as relying on predefined concepts and explaining only a limited set of patterns. To address this, we propose a novel framework, LOGICXGNN, for extracting interpretable logic rules from GNNs. LOGICXGNN is model-agnostic, efficient, and data-driven, eliminating the need for predefined concepts. More importantly, it can serve as a rule-based classifier and even outperform the original neural models. Its interpretability facilitates knowledge discovery, as demonstrated by its ability to extract detailed and accurate chemistry knowledge that is often overlooked by existing methods. Another key advantage of LOGICXGNN is its ability to generate new graph instances in a controlled and transparent manner, offering significant potential for applications such as drug design. We empirically demonstrate these merits through experiments on real-world datasets such as MUTAG and BBBP.

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: 6 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 6 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 3 where our contract draft was wrong; 3 where the contract check could not run; failures of Syntology's instrument, not of the code. Every run on this page is a failure of Syntology's instrument, not of the code.

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

allengeng123/LogicXGNN found in paper text by SyntologySyntology: 7 samples, 6 ran (6 instrument-failed) · 1 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: 6 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 6 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Every run on this page is a failure 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.

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

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 allengeng123/LogicXGNN. “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.

allengeng123/LogicXGNN found in paper text by Syntology 7 samples, 6 ran (6 instrument-failed) · 1 unverified
create_expanded_encoding grounding.py ran · our draft was wrong no licence file found · pointer only · 0fb0f8056142c95e · report fixture: signature x_tensor:Tensor/2/float, node_indices_or_tuple:int/0/int, num_features:int/0/int · returned Tensor · level recorded 2026-09-22
handle_no_unique_nodes_case grounding.py ran · our draft was wrong no licence file found · pointer only · 97c2b59861e2f6e1 · report fixture: signature edge_list:list/1/tuple, multi_orbits:list/1/frozenset, label_map:dict/0/?, G:Graph/0/? · returned tuple · level recorded 2026-09-24
merge_orbits_by_distance_with_paths grounding.py ran; the contract check could not run (RAISES) no licence file found · pointer only · f3b276758079b08a · report fixture: signature edge_list:list/1/tuple, orbits_sorted:list/1/frozenset, label_map:dict/0/? · returned tuple · level recorded 2026-09-24
plot_k_hop_subgraph grounding.py ran · our draft was wrong no licence file found · pointer only · 97073fdd8279a8e5 · report fixture: signature graph_idx:int/0/int, center_index:int/0/int, x_dict:dict/0/?, edge_dict:dict/0/?, atom_type_dict:dict/0/?, nodes_attr:bool/0/bool, title_:str/0/str, k:int/0/int, plot:bool/0/bool, show_node_idx:bool/0/bool, ax:NoneType/0/?, title_position:str/0/str, grounding:bool/0/bool · returned tuple · level recorded 2026-09-22
predicate_features_z grounding.py ran; the contract check could not run (RAISES) no licence file found · pointer only · 702455ee1909aa03 · report fixture: signature x_tensor:Tensor/2/float, merged_orbits:list/1/frozenset · returned Tensor · level recorded 2026-09-22
stable_orbits_with_anchor grounding.py ran; the contract check could not run (RAISES) no licence file found · pointer only · 5c6a2fbe120a6d53 · report fixture: signature edge_list:list/1/tuple, anchor:int/0/int · returned tuple · level recorded 2026-09-22
get_the_rule_iso_z grounding.py unverified no licence file found · pointer only · 4140724d77297ee2 · report

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 LOGICXGNN (graph method: LOGICXGNN). 7 bricks; individually on a fixture: 6 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 6 where Syntology's instrument failed) · 1 unverified. The assembly has not been run end-to-end.

  1. get_the_rule_iso_z entry · level 0 · unverified · 4140724d77297ee2
  2. merge_orbits_by_distance_with_paths helper · level 1 · ran; the contract check could not run (RAISES) · f3b276758079b08a
  3. plot_k_hop_subgraph helper · level 1 · ran · our draft was wrong · 97073fdd8279a8e5
  4. predicate_features_z helper · level 1 · ran; the contract check could not run (RAISES) · 702455ee1909aa03
  5. stable_orbits_with_anchor helper · level 1 · ran; the contract check could not run (RAISES) · 5c6a2fbe120a6d53
  6. handle_no_unique_nodes_case helper · level 1 · ran · our draft was wrong · 97c2b59861e2f6e1
  7. create_expanded_encoding helper · level 1 · ran · our draft was wrong · 0fb0f8056142c95e

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.19476") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Drug DesignDrug Discovery

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

SET

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