Papers › GNNExplainer: Generating Explanations for Graph Neural Networks
GNNExplainer: Generating Explanations for Graph Neural Networks
Rex Ying, Dylan Bourgeois, Jiaxuan You, Marinka Zitnik, Jure Leskovec
Graph Neural Networks (GNNs) are a powerful tool for machine learning on graphs.GNNs combine node feature information with the graph structure by recursively passing neural messages along edges of the input graph. However, incorporating both graph structure and feature information leads to complex models, and explaining predictions made by GNNs remains unsolved. Here we propose GNNExplainer, the first general, model-agnostic approach for providing interpretable explanations for predictions of any GNN-based model on any graph-based machine learning task. Given an instance, GNNExplainer identifies a compact subgraph structure and a small subset of node features that have a crucial role in GNN's prediction. Further, GNNExplainer can generate consistent and concise explanations for an entire class of instances. We formulate GNNExplainer as an optimization task that maximizes the mutual information between a GNN's prediction and distribution of possible subgraph structures. Experiments on synthetic and real-world graphs show that our approach can identify important graph structures as well as node features, and outperforms baselines by 17.1% on average. GNNExplainer provides a variety of benefits, from the ability to visualize semantically relevant structures to interpretability, to giving insights into errors of faulty GNNs.
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):
get_harvested_code_for_paper(arxiv_id="1903.03894")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="1903.03894", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="1903.03894")
Code
Syntology 22 code samples harvested from 5 repositories linked to this paper: 18 ran (of which 0 constructed an object rather than computing a result; 17 with no instrument failure: 0 honoured, 0 violated, 17 with no contract checked; 1 where Syntology's instrument failed) · 4 unverified. Where Syntology's instrument failed: 1 where the contract check could not run; failures of Syntology's instrument, not of the code.
By repository: official repository: 9 samples from 1 repository, 7 ran (7 with no instrument failure; 0 where Syntology's instrument failed); community (archive-listed): 13 samples from 4 repositories, 11 ran (10 with no instrument failure; 1 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.
No sample is linked to this paper from 3 of its repositories that Syntology harvested for other papers:
- LarsHoldijk/RE-ParameterizedExplainerForGraphNeuralNetworks, community (archive-listed): harvested for another paper, listed under the repository
- realmoana/proxyexplainer, community (archive-listed): harvested for another paper, listed under the repository
- dmlc/dgl, community (archive-listed): harvested for 6 other papers, listed under the repository
Levels written between 2026-09-24 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.
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.
A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.
Code Syntology ran Syntology
22 samples harvested: 18 ran (of which 0 constructed an object rather than computing a result; 17 with no instrument failure: 0 honoured, 0 violated, 17 with no contract checked; 1 where Syntology's instrument failed) · 4 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.
Licence: 1 of the 22 samples is pointer only, meaning Syntology does not serve that copy's text. For that sample, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.
Harvested from 5 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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.
A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.
b5d664d8043db74c · report
fixture: signature save_dir:str/0/str, args:Args/0/?, isbest:bool/0/bool, num_epochs:int/0/int · returned str · level recorded 2026-09-25 07dd564321cae261 · report
fixture: signature x:list/1/Tensor, decay:float/0/float · returned list · level recorded 2026-09-25 4d79e3489891364a · report
fixture: signature args:SimpleArgs/0/? · returned str · level recorded 2026-09-25 b787b2d1149916ac · report
fixture: signature args:Args/0/? · returned str · level recorded 2026-09-25 aeb67cb379f56302 · report
fixture: signature adj:ndarray/2/float, n_hops:int/0/int, use_cuda:bool/0/bool · returned ndarray · level recorded 2026-09-25 census: 4 implementations from 5 papers, 4 distinct outputs across 2 buckets, one shared input per bucket gengraph.py ran Apache-2.0 (permissive) ·
11e1d48886273577 · report
fixture: signature graph_list:list/1/Graph, p:float/0/float · returned list · level recorded 2026-09-25 c872f4cd90fce281 · report
fixture: signature input:Tensor/4/float, tv_beta:float/0/float · returned Tensor · level recorded 2026-09-25 9e838e040242f5eb · report
fixture: signature G1:Graph/0/?, G2:Graph/0/?, n_pert_edges:int/0/int · returned Graph · level recorded 2026-09-24 ea9f4e76fa4b2cdf · report
fixture: signature data:callable/0/?, weighted_edge_mask:Tensor/1/float, node_explanations:ndarray/1/float, neighbours:Tensor/1/int, node_idx:int/0/int, feat:Tensor/2/float, label:Tensor/1/int, threshold_num:int/0/int · returned DiGraph · level recorded 2026-09-24 2da026cd7d9d780d · report
fixture: signature noise_feats:list/1/float, label:str/0/str, ymax:float/0/float, color:str/0/str, title:str/0/str, save_path:NoneType/0/? · returned Axes · level recorded 2026-09-24 9d2a8b77cbe3adb0 · report
fixture: signature row:MockRow/0/? · returned list · level recorded 2026-09-24 f2e7e16c79c41137 · report
fixture: signature x:str/0/str · returned bool · level recorded 2026-09-24 3e89f6550fc6950a · report
fixture: signature df_icd:DataFrame/0/?, code:str/0/str · returned str · level recorded 2026-09-24 725051c1c5a70fdf · report
fixture: signature log_dir:str/0/str, name:str/0/str · returned Logger · level recorded 2026-09-24 cd9f64817c619200 · report
fixture: signature base_dir:str/0/str, training:bool/0/bool, id_max:int/0/int · returned str · level recorded 2026-09-24 d95d163bbf721125 · report
fixture: signature args:MockArgs/0/?, training:bool/0/bool, standardize:bool/0/bool, rgb:bool/0/bool · returned list · level recorded 2026-09-24 7dfa7b4c71704350 · report
fixture: signature output:Tensor/3/float, lengths:Tensor/1/int, batch_first:bool/0/bool · returned Tensor · level recorded 2026-09-24 362713dfa016e305 · report
fixture: signature batch_size:int/0/int, transform:callable/0/?, csv_file:str/0/str, file_col_name:str/0/str, num_workers:int/0/int · returned DataLoader · level recorded 2026-09-24 Tasks
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