Papers › Temporal Knowledge Base Completion: New Algorithms and Evaluation Protocols

Temporal Knowledge Base Completion: New Algorithms and Evaluation Protocols

2 May 2020EMNLP 2020 11arXiv:2005.05035archive 2025-07-28

Prachi Jain, Sushant Rathi, Mausam, Soumen Chakrabarti

Temporal knowledge bases associate relational (s,r,o) triples with a set of times (or a single time instant) when the relation is valid. While time-agnostic KB completion (KBC) has witnessed significant research, temporal KB completion (TKBC) is in its early days. In this paper, we consider predicting missing entities (link prediction) and missing time intervals (time prediction) as joint TKBC tasks where entities, relations, and time are all embedded in a uniform, compatible space. We present TIMEPLEX, a novel time-aware KBC method, that also automatically exploits the recurrent nature of some relations and temporal interactions between pairs of relations. TIMEPLEX achieves state-of-the-art performance on both prediction tasks. We also find that existing TKBC models heavily overestimate link prediction performance due to imperfect evaluation mechanisms. In response, we propose improved TKBC evaluation protocols for both link and time prediction tasks, dealing with subtle issues that arise from the partial overlap of time intervals in gold instances and system predictions.

PaperPDFConference PDFCodeCode 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 12 code samples harvested from 1 repository linked to this paper: 3 ran (of which 1 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 2 where Syntology's instrument failed) · 9 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

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

dair-iitd/tkbi officialmentioned in papermentioned on GitHubpytorchSyntology: 12 samples, 3 ran (2 instrument-failed) · 9 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

12 samples harvested: 3 ran (of which 1 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 2 where Syntology's instrument failed) · 9 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 · our draft was wrong
1ran; the contract check could not run
1ran
9unverified

Licence: 12 of the 12 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 dair-iitd/tkbi. “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.

dair-iitd/tkbi official repository 12 samples, 3 ran (2 instrument-failed) · 9 unverified
TimePlex_base models.py ran · metamorphic tier: deterministic no licence file found · pointer only · 07ea1c3eff122d6d · report fixture: returned TimePlex_base · level recorded 2026-09-22
func_load_to_gpu models.py ran; the contract check could not run (RAISES) fingerprinted no licence file found · pointer only · 2dd23c60c69e6933 · report fixture: signature data:Tensor/2/float, load_to_gpu:bool/0/bool · returned Tensor · level recorded 2026-09-22
get_pairwise_r_dict models.py ran · our draft was wrong no licence file found · pointer only · 031befc1f164bdbc · report fixture: signature ent_rel_dict_t1:dict/0/?, ent_rel_dict_t2:dict/0/? · returned dict · level recorded 2026-09-22
Gadget models.py unverified no licence file found · pointer only · 08b4bc511b937540 · report
Pairs models.py unverified no licence file found · pointer only · 765b061b7b2bc7e3 · report
ProbDensityScorer models.py unverified no licence file found · pointer only · e29621e5e0a2e8fa · report
Recurrent in 5 papers models.py unverified no licence file found · pointer only · 071c7df25b2bb31b · report
RecurringFactScorer models.py unverified no licence file found · pointer only · 71a1315ced027a2b · report
TimePlex models.py unverified no licence file found · pointer only · 436de3b3c8149244 · report
mean_variance models.py unverified no licence file found · pointer only · 1ec8e7a5004409db · report
recurring_mean_variance models.py unverified no licence file found · pointer only · 3a3bec30bf828f97 · report
recurring_relation_mean_variance models.py unverified no licence file found · pointer only · 9605604fe19b6c37 · 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 TIMEPLEX (graph method: TIMEPLEX). 12 bricks; individually on a fixture: 3 ran (of which 1 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 2 where Syntology's instrument failed) · 9 unverified. The assembly has not been run end-to-end.

  1. TimePlex entry · level 0 · unverified · 436de3b3c8149244
  2. Pairs helper · level 0 · unverified · 765b061b7b2bc7e3
  3. Recurrent helper · level 0 · unverified · 071c7df25b2bb31b
  4. TimePlex_base model · level 1 · ran · 07ea1c3eff122d6d
  5. Gadget helper · level 0 · unverified · 08b4bc511b937540
  6. ProbDensityScorer helper · level 0 · unverified · e29621e5e0a2e8fa
  7. func_load_to_gpu helper · level 1 · ran; the contract check could not run (RAISES) · 2dd23c60c69e6933
  8. RecurringFactScorer helper · level 0 · unverified · 71a1315ced027a2b
  9. mean_variance helper · level 0 · unverified · 1ec8e7a5004409db
  10. recurring_mean_variance helper · level 0 · unverified · 3a3bec30bf828f97
  11. recurring_relation_mean_variance helper · level 0 · unverified · 9605604fe19b6c37
  12. get_pairwise_r_dict helper · level 1 · ran · our draft was wrong · 031befc1f164bdbc

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

Tasks

Knowledge Base CompletionKnowledge Graph CompletionKnowledge GraphsLink PredictionPredictionTemporal Information ExtractionTemporal Knowledge Graph CompletionTime-interval Prediction

1 archive task tag without a task page not shown.

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Link Prediction ICEWS05-15 TimePlex MRR 0.632 #5 of 16 Archive leaderboard report
Link Prediction ICEWS14 TimePlex MRR 0.589 #5 of 16 Archive leaderboard report
Link Prediction Wikidata12k TimePlex MRR 0.3335 #1 of 1 Archive leaderboard report
Link Prediction Yago11k TimePlex MRR 0.2364 #1 of 1 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