Papers › MEIM: Multi-partition Embedding Interaction Beyond Block Term Format for Efficient and...

MEIM: Multi-partition Embedding Interaction Beyond Block Term Format for Efficient and Expressive Link Prediction

30 Sep 2022arXiv:2209.15597archive 2025-07-28

Hung Nghiep Tran, Atsuhiro Takasu

Knowledge graph embedding aims to predict the missing relations between entities in knowledge graphs. Tensor-decomposition-based models, such as ComplEx, provide a good trade-off between efficiency and expressiveness, that is crucial because of the large size of real world knowledge graphs. The recent multi-partition embedding interaction (MEI) model subsumes these models by using the block term tensor format and provides a systematic solution for the trade-off. However, MEI has several drawbacks, some of which carried from its subsumed tensor-decomposition-based models. In this paper, we address these drawbacks and introduce the Multi-partition Embedding Interaction iMproved beyond block term format (MEIM) model, with independent core tensor for ensemble effects and soft orthogonality for max-rank mapping, in addition to multi-partition embedding. MEIM improves expressiveness while still being highly efficient, helping it to outperform strong baselines and achieve state-of-the-art results on difficult link prediction benchmarks using fairly small embedding sizes. The source code is released at https://github.com/tranhungnghiep/MEIM-KGE.

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

The archive's official repository (tranhungnghiep/meim-kge) was not harvested; the 7 samples below come from 1 repository the archive does not mark official.

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

By repository: found in paper text by Syntology: 7 samples from 1 repository, 6 ran (1 with no instrument failure; 5 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.

tranhungnghiep/meim-kge officialmentioned in papermentioned on GitHubpytorchSyntology: not harvested report
tranhungnghiep/AnalyzeKGE mentioned on GitHubtfSyntology: not harvested report
tranhungnghiep/AnalyzingKGEmbeddings mentioned on GitHubtfSyntology: not harvested report
tranhungnghiep/MEI-KGE mentioned on GitHubpytorchSyntology: 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: 6 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 1 honoured, 0 violated, 0 with no contract checked; 5 where Syntology's instrument failed) · 1 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 · our draft was wrong
3ran; the contract check could not run
1unverified

Licence: 7 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 tranhungnghiep/MEIM. “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.

tranhungnghiep/MEIM found in paper text by Syntology 7 samples, 6 ran (5 instrument-failed) · 1 unverified
minmaxnorm src/models.py ran · our draft was wrong fingerprinted no licence file found · pointer only · 8e31d4ebb7707359 · report fixture: signature x:Tensor/2/float, dim:int/0/int, p:float/0/float, min_norm:float/0/float, max_norm:float/0/float, epsilon:float/0/float · returned Tensor · level recorded 2026-09-22
nonneg src/models.py ran · honoured contract fingerprinted no licence file found · pointer only · a52f42be139e917d · report fixture: signature x:Tensor/2/float · returned Tensor · level recorded 2026-09-22
softmax_cross_entropy_with_softtarget src/models.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant no licence file found · pointer only · 45dd43505b557df3 · report fixture: signature input:Tensor/2/float, target:Tensor/2/float, reduction:str/0/str · returned Tensor · level recorded 2026-09-22
to_torch in 53 papers
census: 5 implementations from 6 papers, 2 distinct outputs across 2 buckets, one shared input per bucket this sample: bucket 2 of 2, arg 1: rank 2, kind float, dtype float32
src/models.py ran; the contract check could not run (RAISES) no licence file found · pointer only · 22bc6af5706e2818 · report fixture: signature a:ndarray/2/float, device:str/0/str · returned Tensor · level recorded 2026-09-22
truncated_normal_ in 8 papers src/models.py ran; the contract check could not run (RAISES) fingerprinted no licence file found · pointer only · 3ca0782c847afb07 · report fixture: signature tensor:Tensor/2/float, myclip_a:int/0/int, myclip_b:int/0/int, my_mean:float/0/float, my_std:float/0/float · returned Tensor · level recorded 2026-09-22
unitnorm src/models.py ran · our draft was wrong fingerprinted no licence file found · pointer only · 2efde740d8cc2b74 · report fixture: signature x:Tensor/2/float, dim:int/0/int, p:float/0/float, epsilon:float/0/float · returned Tensor · level recorded 2026-09-22
MEI src/models.py unverified no licence file found · pointer only · c135c271d9027066 · 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 MEIM (graph method: MEIM). 7 bricks; individually on a fixture: 6 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 1 honoured, 0 violated, 0 with no contract checked; 5 where Syntology's instrument failed) · 1 unverified. The assembly has not been run end-to-end.

  1. MEI entry · level 0 · unverified · c135c271d9027066
  2. minmaxnorm helper · level 1 · ran · our draft was wrong · 8e31d4ebb7707359
  3. nonneg helper · level 1 · ran · honoured contract · a52f42be139e917d
  4. softmax_cross_entropy_with_softtarget helper · level 1 · ran; the contract check could not run (RAISES) · 45dd43505b557df3
  5. to_torch helper · level 1 · ran; the contract check could not run (RAISES) · 22bc6af5706e2818
  6. truncated_normal_ helper · level 1 · ran; the contract check could not run (RAISES) · 3ca0782c847afb07
  7. unitnorm helper · level 1 · ran · our draft was wrong · 2efde740d8cc2b74

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

Tasks

Graph EmbeddingKnowledge Graph EmbeddingKnowledge GraphsLink PredictionTensor DecompositionWorld Knowledge

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Link Prediction FB15k-237 MEIM Hits@1 0.274 #11 of 75 Archive leaderboard report
Link Prediction FB15k-237 MEIM Hits@10 0.557 #11 of 75 Archive leaderboard report
Link Prediction FB15k-237 MEIM Hits@3 0.406 #11 of 75 Archive leaderboard report
Link Prediction FB15k-237 MEIM MRR 0.369 #11 of 75 Archive leaderboard report
Link Prediction WN18RR MEIM Hits@1 0.458 #31 of 75 Archive leaderboard report
Link Prediction WN18RR MEIM Hits@10 0.577 #31 of 75 Archive leaderboard report
Link Prediction WN18RR MEIM Hits@3 0.518 #31 of 75 Archive leaderboard report
Link Prediction WN18RR MEIM MRR 0.499 #31 of 75 Archive leaderboard report
Link Prediction YAGO3-10 MEIM Hits@1 0.514 #1 of 18 Archive leaderboard report
Link Prediction YAGO3-10 MEIM Hits@10 0.716 #1 of 18 Archive leaderboard report
Link Prediction YAGO3-10 MEIM Hits@3 0.625 #1 of 18 Archive leaderboard report
Link Prediction YAGO3-10 MEIM MRR 0.585 #1 of 18 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.

Methods

MEI

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