Papers › RippleNet: Propagating User Preferences on the Knowledge Graph for Recommender Systems

RippleNet: Propagating User Preferences on the Knowledge Graph for Recommender Systems

9 Mar 2018arXiv:1803.03467archive 2025-07-28

Hongwei Wang, Fuzheng Zhang, Jialin Wang, Miao Zhao, Wenjie Li, Xing Xie, Minyi Guo

To address the sparsity and cold start problem of collaborative filtering, researchers usually make use of side information, such as social networks or item attributes, to improve recommendation performance. This paper considers the knowledge graph as the source of side information. To address the limitations of existing embedding-based and path-based methods for knowledge-graph-aware recommendation, we propose Ripple Network, an end-to-end framework that naturally incorporates the knowledge graph into recommender systems. Similar to actual ripples propagating on the surface of water, Ripple Network stimulates the propagation of user preferences over the set of knowledge entities by automatically and iteratively extending a user's potential interests along links in the knowledge graph. The multiple "ripples" activated by a user's historically clicked items are thus superposed to form the preference distribution of the user with respect to a candidate item, which could be used for predicting the final clicking probability. Through extensive experiments on real-world datasets, we demonstrate that Ripple Network achieves substantial gains in a variety of scenarios, including movie, book and news recommendation, over several state-of-the-art baselines.

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

By repository: official repository: 3 samples from 1 repository, 1 ran (1 with no instrument failure; 0 where Syntology's instrument failed); community (archive-listed): 4 samples from 2 repositories, 2 ran (2 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 between 2026-09-22 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

hwwang55/RippleNet officialmentioned in papermentioned on GitHubtfMITSyntology: 3 samples, 1 ran (0 instrument-failed) · 2 unverified report
Hank-Kuo/RippleNet mentioned on GitHubpytorchSyntology: 1 sample, 1 ran (0 instrument-failed) · 0 unverified report
Jessinra/GDP-RippleNet mentioned on GitHubtfSyntology: not harvested report
Jessinra/GDP-RippleNet-Ori mentioned on GitHubtfSyntology: not harvested report
ZJJHYM/RippleNet mentioned on GitHubtfMITSyntology: not harvested report
johnnyjana730/MVIN mentioned on GitHubtfSyntology: not harvested report
qibinc/RippleNet-PyTorch mentioned on GitHubpytorchSyntology: not harvested report
sdu-wjh/icws2020 mentioned on GitHubtfMITSyntology: 3 samples, 1 ran (0 instrument-failed) · 2 unverified report
tezignlab/RippleNet-TF2 mentioned on GitHubtfMITSyntology: not harvested 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: 3 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 1 honoured, 0 violated, 2 with no contract checked; 0 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 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.

1ran · honoured contract
2ran
4unverified

Licence: 1 of the 7 samples is 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 3 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.

hwwang55/RippleNet official repository 3 samples, 1 ran (0 instrument-failed) · 2 unverified
dataset_split in 12 papers src/data_loader.py ran MIT (permissive) · 3807a263b7505930 · report fixture: signature rating_np:ndarray/2/int · returned tuple · level recorded 2026-09-25
load_data in 700 papers src/data_loader.py unverified MIT (permissive) · 27c466797c997173 · report
load_rating src/data_loader.py unverified MIT (permissive) · c526b09d6c58d0dc · report
Hank-Kuo/RippleNet community (archive-listed) 1 sample, 1 ran (0 instrument-failed) · 0 unverified
evaluation in 57 papers evaluate.py ran · honoured contract no licence file found · pointer only · a863327019290a51 · report fixture: signature params:Params/0/?, model:callable/0/?, data_generator:list/1/tuple · returned tuple · level recorded 2026-09-22
sdu-wjh/icws2020 community (archive-listed) 3 samples, 1 ran (0 instrument-failed) · 2 unverified
dataset_split in 12 papers src/data_loader.py ran MIT (permissive) · cfb25fac458f2b48 · report fixture: signature rating_np:ndarray/2/int, kg:dict/0/? · returned tuple · level recorded 2026-09-26
load_data in 700 papers src/data_loader.py unverified MIT (permissive) · 0cd23296b20e4497 · report
load_rating src/data_loader.py unverified MIT (permissive) · bd6a37c39c9dc99d · report

Tasks

Click-Through Rate PredictionCollaborative FilteringNews RecommendationRecommendation Systems

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Click-Through Rate Prediction Bing News RippleNet AUC 0.678 #5 of 7 Archive leaderboard report
Click-Through Rate Prediction Bing News RippleNet Accuracy 63.2 #5 of 7 Archive leaderboard report
Click-Through Rate Prediction Book-Crossing RippleNet AUC 0.729 #2 of 2 Archive leaderboard report
Click-Through Rate Prediction Book-Crossing RippleNet Accuracy 0.662 #2 of 2 Archive leaderboard report
Click-Through Rate Prediction MovieLens 1M RippleNet AUC 0.921 #3 of 6 Archive leaderboard report
Click-Through Rate Prediction MovieLens 1M RippleNet Accuracy 84.4 #3 of 6 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

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