Papers › Subgraph Neighboring Relations Infomax for Inductive Link Prediction on Knowledge Graphs

Subgraph Neighboring Relations Infomax for Inductive Link Prediction on Knowledge Graphs

28 Jul 2022arXiv:2208.00850archive 2025-07-28

Xiaohan Xu, Peng Zhang, Yongquan He, Chengpeng Chao, Chaoyang Yan

Inductive link prediction for knowledge graph aims at predicting missing links between unseen entities, those not shown in training stage. Most previous works learn entity-specific embeddings of entities, which cannot handle unseen entities. Recent several methods utilize enclosing subgraph to obtain inductive ability. However, all these works only consider the enclosing part of subgraph without complete neighboring relations, which leads to the issue that partial neighboring relations are neglected, and sparse subgraphs are hard to be handled. To address that, we propose Subgraph Neighboring Relations Infomax, SNRI, which sufficiently exploits complete neighboring relations from two aspects: neighboring relational feature for node feature and neighboring relational path for sparse subgraph. To further model neighboring relations in a global way, we innovatively apply mutual information (MI) maximization for knowledge graph. Experiments show that SNRI outperforms existing state-of-art methods by a large margin on inductive link prediction task, and verify the effectiveness of exploring complete neighboring relations in a global way to characterize node features and reason on sparse subgraphs.

PaperPDFCodeCode 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 10 code samples harvested from 1 repository linked to this paper: 7 ran (of which 7 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 0 where Syntology's instrument failed) · 3 unverified; every one of the 7 samples that ran constructed an object rather than computing a result. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 10 samples from 1 repository, 7 ran (7 with no instrument failure; 0 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.

Tebmer/SNRI officialmentioned on GitHubpytorchSyntology: 10 samples, 7 ran (0 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

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

7ran
3unverified

Licence: 10 of the 10 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 Tebmer/SNRI. “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: for a class the fixture built without calling, the harness called the object with inputs it made up itself, so the recorded signature is the harness's probe, not the fixture's arguments. “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.

Tebmer/SNRI official repository 10 samples, 7 ran (0 instrument-failed) · 3 unverified
Aggregator in 13 papers model/dgl/graph_classifier.py ran no licence file found · pointer only · d46dff6f46c30ccc · report fixture: returned Aggregator · level recorded 2026-09-22
BatchGRU model/dgl/graph_classifier.py ran no licence file found · pointer only · 3435ce02c9a39883 · report fixture: returned BatchGRU · level recorded 2026-09-22
Discriminator in 42 papers model/dgl/graph_classifier.py ran no licence file found · pointer only · d58499a1c7e73bae · report fixture: returned Discriminator · level recorded 2026-09-22
GRUAggregator model/dgl/graph_classifier.py ran no licence file found · pointer only · 8a3af90773c72327 · report fixture: returned GRUAggregator · level recorded 2026-09-22
Identity in 49 papers
census: 10 implementations from 13 papers, 4 distinct outputs across 4 buckets, one shared input per bucket
model/dgl/graph_classifier.py ran fingerprinted no licence file found · pointer only · df20ae228378ef18 · report fixture: returned Identity · level recorded 2026-09-22
MLPAggregator model/dgl/graph_classifier.py ran no licence file found · pointer only · 82fd85090dac6db9 · report fixture: returned MLPAggregator · level recorded 2026-09-22
SumAggregator model/dgl/graph_classifier.py ran no licence file found · pointer only · 89a158e1fe91f82a · report fixture: returned SumAggregator · level recorded 2026-09-22
GraphClassifier model/dgl/graph_classifier.py unverified no licence file found · pointer only · 9771c2055d849ed6 · report
RGCN in 5 papers model/dgl/graph_classifier.py unverified no licence file found · pointer only · 73029d39434303a6 · report
RGCNLayer model/dgl/graph_classifier.py unverified no licence file found · pointer only · 4eab4e0975e40901 · 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 Subgraph Neighboring Relations Infomax (SNRI) (graph method: Subgraph Neighboring Relations Infomax (SNRI)). 10 bricks; individually on a fixture: 7 ran (of which 7 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 0 where Syntology's instrument failed) · 3 unverified; every one of the 7 samples that ran constructed an object rather than computing a result. The assembly has not been run end-to-end.

  1. GraphClassifier entry · level 0 · unverified · 9771c2055d849ed6
  2. BatchGRU helper · level 1 · ran · 3435ce02c9a39883
  3. Discriminator model · level 1 · ran · d58499a1c7e73bae
  4. RGCN model · level 0 · unverified · 73029d39434303a6
  5. GRUAggregator helper · level 1 · ran · 8a3af90773c72327
  6. MLPAggregator helper · level 1 · ran · 82fd85090dac6db9
  7. RGCNLayer model · level 0 · unverified · 4eab4e0975e40901
  8. SumAggregator helper · level 1 · ran · 89a158e1fe91f82a
  9. Aggregator helper · level 1 · ran · d46dff6f46c30ccc
  10. Identity helper · level 1 · ran · df20ae228378ef18

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

Tasks

Inductive Link PredictionKnowledge GraphsLink Prediction

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