Methods › Graphs › Graph Models › Graph Convolutional Networks

Graph Convolutional Networks

388 papers tagged archive 2025-07-28

archive 2025-07-28 Description, source and code snippet are the archive's method entry.

A Graph Convolutional Network, or GCN, is an approach for semi-supervised learning on graph-structured data. It is based on an efficient variant of convolutional neural networks which operate directly on graphs.

Image source: Semi-Supervised Classification with Graph Convolutional Networks

Source: Semi-Supervised Classification with Graph Convolutional Networks

In Syntology repository known, no verified implementation (declared_code; repositories: 5 listed of 53 in the graph, strongest link: official). The archive credits no paper with an arXiv id for this method, so whether this answer (about arXiv:1609.02907) is about this method is not checked.

Code Syntology holds under other names, as the lookup lists them (code_nearby); not a complete list, and none of them is this method.

Origin paper of this answer, arXiv:1609.02907 (its page on this site · its page on Syntology): Syntology's run record for its harvested code, 39 ran (of which 13 constructed an object rather than computing a result; 34 with no instrument failure: 0 honoured, 1 violated, 33 with no contract checked; 5 where Syntology's instrument failed) · 19 unverified (of 58 harvested samples) · 23 pointer-only (licence). The instrument figure counts failures of Syntology's instrument, not of the code. Ran means executed on a synthesized input, not that the code is correct.

Syntology's have check for this name (free, it answers coverage only), read 2026-10-05; ask it again live. A level is the served verification level of that one answer; nothing here is summed across methods.

What each level means, quoted from Syntology's server card: V0 “imports”; V1 “executes against a synthesized fixture and returns a value of the recorded type”; V2 “two implementations GENERATED from the paper's signature and spec agree numerically (1e-6) on fixture inputs” “neither of the two ever read the authors' own code, so V2 measures how unambiguously the paper specifies the method, not fidelity to the authors' implementation (measured 2026-09-11, commit 75eaa77: cross_checked_by is a second LLM on 2,628 of 2,831 served samples)”; V3 “paper-derived property tests pass on both of those same two generations.” The card adds: “No rung on this ladder compares the served code against the authors' implementation, so treat every level as evidence about runnability and internal agreement, not about matching the paper's results.” A level quoted in two parts is one definition the card writes as two clauses joined by a double hyphen, each clause quoted on its own (how these levels are quoted).

Papers archive 2025-07-28

archive papers tagged: 388 · with a code link: 178 · where Syntology ran a sample: 56 (48 with a run with no instrument failure, 8 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (56 of 388 tagged: 48 with a run with no instrument failure, 8 where every run was a failure of Syntology's instrument)

Page 1 of 4: papers 1 to 100 of 388, newest first by the archive's date (ties by slug), in archive order.

Repository counts are the archive's code-links table. A Syntology line states what Syntology ran from that paper's harvested code, as “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. It is per sample and not a correctness claim. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from.

Tasks archive 2025-07-28

20 shown of 325 tasks the archive attaches to papers tagged with this method, by distinct papers. A task without a page in the catalog is plain text.

TaskPapers
Node Classification63
General Classification50
Classification33
Representation Learning32
Action Recognition25
Link Prediction21
Skeleton Based Action Recognition21
Graph Embedding20
Clustering19
Graph Attention19
Graph Classification19
Recommendation Systems19
Knowledge Graphs18
Prediction18
Sentence17
Graph Learning15
Graph Neural Network13
Attribute12
Graph Representation Learning12
Relation12

Usage over time archive 2025-07-28

Papers per year tagged with Graph Convolutional Networks: 2016 to 2021, peak 137 137 0 2016: 1 paper 2016 2017: 1 paper 2017 2018: 33 papers 2018 2019: 111 papers 2019 2020: 137 papers 2020 2021: 105 papers 2021
Papers per year the archive tags with this method, by the paper's archive date (388 dated). Bars are counts, not a trend claim.

Components: the archive holds no method-to-method composition, so PwC's Components table cannot be rebuilt; the Papers list carries no Results column for the same reason (the archive does not join its leaderboard rows to method tags).

Categories archive 2025-07-28

Graph Models

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