Papers › A Re-evaluation of Knowledge Graph Completion Methods

A Re-evaluation of Knowledge Graph Completion Methods

10 Nov 2019ACL 2020 6arXiv:1911.03903archive 2025-07-28

Zhiqing Sun, Shikhar Vashishth, Soumya Sanyal, Partha Talukdar, Yiming Yang

Knowledge Graph Completion (KGC) aims at automatically predicting missing links for large-scale knowledge graphs. A vast number of state-of-the-art KGC techniques have got published at top conferences in several research fields, including data mining, machine learning, and natural language processing. However, we notice that several recent papers report very high performance, which largely outperforms previous state-of-the-art methods. In this paper, we find that this can be attributed to the inappropriate evaluation protocol used by them and propose a simple evaluation protocol to address this problem. The proposed protocol is robust to handle bias in the model, which can substantially affect the final results. We conduct extensive experiments and report the performance of several existing methods using our protocol. The reproducible code has been made publicly available

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

By repository: official repository: 7 samples from 1 repository, 5 ran (5 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.

No sample is linked to this paper from 1 of its repositories that Syntology harvested for other papers:

Levels written on 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

svjan5/kg-reeval officialmentioned in papermentioned on GitHubtfApache-2.0Syntology: 7 samples, 5 ran (0 instrument-failed) · 2 unverified report
daiquocnguyen/ConvKB mentioned on GitHubtfSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to A Novel Embedding Model for Knowledge Base Completion Based on Convolutional Neural Network (arXiv:1712.02121; that paper's own run record: 2 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; 2 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method. 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.

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

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

5ran
2unverified

Licence: 0 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 svjan5/kg-reeval. “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.

svjan5/kg-reeval official repository 7 samples, 5 ran (0 instrument-failed) · 2 unverified
assignEmbeddings CapsE/builddata_ecir.py ran Apache-2.0 (permissive) · 8254437f82bb7032 · report fixture: signature lstent:dict/0/?, word_indexes:dict/0/?, embedding_dim:int/0/int · returned ndarray · level recorded 2026-09-25
init_dataset_ecir CapsE/builddata_ecir.py ran Apache-2.0 (permissive) · 24a6fe3889b241f3 · report fixture: signature entinit:str/0/str · returned dict · level recorded 2026-09-25
parse_line in 17 papers CapsE/builddata_softplus.py ran Apache-2.0 (permissive) · e1642aeda2a336f1 · report fixture: signature line:str/0/str · returned tuple · level recorded 2026-09-25
read_from_id CapsE/builddata_ecir.py ran Apache-2.0 (permissive) · b66238861fb279c7 · report fixture: signature filename:str/0/str · returned tuple · level recorded 2026-09-25
squash in 30 papers
census: 8 implementations from 5 papers, 4 distinct outputs across 2 buckets, one shared input per bucket
CapsE/capsuleLayer.py ran Apache-2.0 (permissive) · ad05325f767d6062 · report fixture: signature vector:EagerTensor/5/float · returned EagerTensor · level recorded 2026-09-25
init_norm_Vector CapsE/builddata_softplus.py unverified Apache-2.0 (permissive) · a4febf650e2dc53c · report
routing CapsE/capsuleLayer.py unverified Apache-2.0 (permissive) · 2cf11cd23f5ddcb6 · report

Tasks

Knowledge Graph CompletionKnowledge GraphsLink Prediction

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Link Prediction FB15k-237 ConvKB (Corrected) Hits@10 .421 #71 of 75 Archive leaderboard report
Link Prediction FB15k-237 ConvKB (Corrected) MR 309 #71 of 75 Archive leaderboard report
Link Prediction FB15k-237 ConvKB (Corrected) MRR .309 #71 of 75 Archive leaderboard report
Link Prediction FB15k-237 KBAT (Corrected) Hits@10 .331 #74 of 75 Archive leaderboard report
Link Prediction FB15k-237 KBAT (Corrected) MR 270 #74 of 75 Archive leaderboard report
Link Prediction FB15k-237 KBAT (Corrected) MRR .157 #74 of 75 Archive leaderboard report
Link Prediction FB15k-237 CapsE (Corrected) Hits@10 .057 #75 of 75 Archive leaderboard report
Link Prediction FB15k-237 CapsE (Corrected) MR 446 #75 of 75 Archive leaderboard report
Link Prediction FB15k-237 CapsE (Corrected) MRR .032 #75 of 75 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