acceptodds
Under review as a conference paper at ICLR 2027

RuleCast: Evidence-Constrained Partner-Role Forecasting for Temporal Link Prediction

Abstract

Existing temporal link predictors aggregate source history and score candidate compatibility, which overlooks the structural regularity of future partner roles. We propose a fundamentally different factorization: future links arise from evidence-constrained partner-role forecasting. First, the source's historical interactions predict the expected behavioral role of its next partner. Second, candidate nodes are grounded by candidate behavior and query-specific historical evidence. Our RuleCast model implements this paradigm with time-varying soft roles and a protocol encoder that forecasts role distributions. It employs specialized experts to model role compatibility, history matching, reciprocity, closure, and periodicity, alongside a candidate-aware routing mechanism that activates only valid evidence-supported experts. A lightweight identity residual preserves transductive node characteristics. Evaluated on ten temporal graph benchmarks, RuleCast consistently improves MRR and improves AP and ROC-AUC on most datasets. Ablations verify that role forecasting and evidence grounding are mutually essential, validating our new paradigm for temporal link prediction.

Primary area:
learning on graphs and other geometries & topologies
Keywords:
Temporal graph learning, temporal link prediction, partner-role forecasting, dynamic behavioral roles

Reviews

Among:
Shape:
1234this paper, Bottom 27%
Figure 1. Mean review rating of the reviewed papers at ICLR 2027. This paper averages 2.00 over 3 reviews, above 27% of the others.
Reviewer_kFAzOpenReview ↗
Rating
2(+1)
Confidence
3
Informativeness
1
Presentation
1
Soundness
2
Read review
Paper summary

The authors consider temporal link prediction and propose to keep track of the "current roles" that nodes play at the points in time when a prediction should be made. They adopt a mixture-of-experts approach and define experts relating to, for example, nodes' history, nodes' behaviour regarding repeated interactions, or nodes' behaviour regarding reciprocity in their interactions. When a query arrives that asks "do node u and v interact at time point t", they check what u's predicted "need for an interaction partner" at time t is and compare that with v's estimated role at that same time t. They do this by using attention to learn a routing mechanism. In their evaluation, the authors consider a standard range of benchmark datasets and TGNN models for temporal link prediction, but focus specifically on benchmarking against CRAFT. The authors' method, RuleCast, achieves competitive performance, and an ablation study shows the importance of properly including aspects such as the nodes' history.

I found the paper somewhat difficult to read: with typically several ideas packaged into the same sentence, it is difficult to figure out what the most important message is. The authors also seem to assume quite some familiarity with mixture-of-experts approaches, which, given ICLR as the venue, seems defensible. However, spending a paragraph on introducing the relevant terminology would have made the paper more accessible.

The three research questions mentioned in section 5 do not appear to be properly answered in the main text. Moreover, the Discussion and Conclusion sections are each merely a short paragraph long. I believe this leaves the reader wondering how to make sense of the present work. What exactly are the aspects RuleCast that make it work well? Why did the authors choose to let CRAFT stand out as the seemingly most important baseline? What are the failure modes of RuleCast, when does it not work well?

Critical strengths

The paper brings established ideas from other areas of deep learning to temporal link prediction, specifically, the mixture-of-experts approach.

Critical weaknesses
  • The writing is dense in the sense that too many ideas are packaged into the same sentence. This makes it unnecessarily hard for the reader to figure out what the authors want to say.
  • The authors did not answer or discuss the three research questions they formulated.
  • The Discussion and Conclusion sections are extremely short, each containing only one short paragraph.
Questions for authors

There are a couple of points that remained unclear to me

  1. Why did you choose to give so much focus to CRAFT in the evaluation? I think this should be explained to the reader.
  2. How small is a "small MLP" typically?
  3. There is a statement in the discussion that I did not understand: "The direct controls isolate the role-protocol factorization from decoder capacity". Could you explain what you mean by this and where you have shown this?
  4. There is another statement, where I'm wondering where the paper shows this: "the expert set covers complementary predictive signatures"? Have you shown that they are complementary? Have you verified that this is the case?
  5. Can you say something about the failure modes of RuleCast? What would be an example where RuleCast doesn't work well? Are there specific patterns we should expect it has problems with?

Minor points

  • Figure 2 is mentioned before Figure 1 in the text, but it appears 2 pages after Figure 1.
  • M is first mentioned in l.135 but not defined until l.212
3 comments
AuthorsOpenReview ↗

Response to Reviewer kFAz

Thank you for the detailed feedback. Your questions helped us clarify the exposition and explain what the experiments establish.

W1: Clarity and Figure 2

The writing is dense in the sense that too many ideas are packaged into the same sentence. This makes it unnecessarily hard for the reader to figure out what the authors want to say.

We revised the exposition in the Introduction and Sections 3–4. The Introduction now separates partner-role forecasting from candidate scoring, and Section 3 explains what the experts score, what the mask excludes, and what the router weights. We redrew Figure 2 to show how the shared forecast and candidate-specific evidence produce the final score. Section 4.4 introduces the figure after the scoring equations.

W2: Answers to the research questions

The authors did not answer or discuss the three research questions they formulated.

Section 5.1 lists RQ1–RQ3 explicitly. RQ1 (Section 5.2): RuleCast has the highest reported MRR on all ten datasets (Table 1) and higher AP and ROC-AUC on nine (Table 2). RQ2 (Section 5.3): RuleCast outperforms direct feature scoring, and the partner sequence helps on UCI and LastFM, where the matched simplex and continuous controls are close. RQ3 (Section 5.4): router weights vary with the available evidence, with the clearest ranking gain over uniform routing for new partners on Flights.

W3: Discussion and conclusion

The Discussion and Conclusion sections are extremely short, each containing only one short paragraph.

We expanded the Discussion (Section 6) to connect the matched controls and the Flights evidence strata with concrete failure modes (see Q5). Section 7 summarizes the shared partner-role forecast, candidate-specific scoring, and MRR gains.

Q1: Why compare with CRAFT

Why did you choose to give so much focus to CRAFT in the evaluation? I think this should be explained to the reader.

CRAFT directly matches each candidate against the source's history. RuleCast instead forecasts a partner-role distribution shared by all candidates before scoring them. CRAFT is also among the strongest baselines in Table 1. Comparing the two helps distinguish how they use history (Introduction and Section 2).

Q2: Expert MLP dimensions

How small is a "small MLP" typically?

We give the dimensions in Section 4.3 and Appendix A: pair experts map two inputs to one score through a 64-unit hidden layer; the history expert has the same width and 193 inputs at d=64d=64. Both use GELU and dropout of 0.1.

Q3: What the direct controls test

There is a statement in the discussion that I did not understand: "The direct controls isolate the role-protocol factorization from decoder capacity". Could you explain what you mean by this and where you have shown this?

"Isolate" was too strong: the architectures and parameter counts differ. We meant to test whether Feature-MLP's direct scoring could match RuleCast's partner-role forecasting and grounding. Section 5.2 now says the controls "compare other scoring architectures under the same evaluation settings" (split, sampler, evaluator). RuleCast ranks higher on five datasets (Table 7 and Appendix H text). Appendix J illustrates the role forecast and expert contributions. Table 8 matches parameter counts for simplex and continuous scoring on UCI and LastFM; their results are close.

Q4: Evidence complementarity

There is another statement, where I'm wondering where the paper shows this: "the expert set covers complementary predictive signatures"? Have you shown that they are complementary? Have you verified that this is the case?

Table 9 masks expert groups at a fixed checkpoint with the same candidates, without retraining. When the true partner has both evidence types, adding history to Role + Pair raises MRR by 0.15 points on Flights and 0.03 on Wikipedia. When it has only history evidence on Wikipedia, adding history to Role raises MRR by 2.26 points. Pair evidence accounts for most of the overall gain, and the first comparison shows that history can complement it (Section 5.4 and Appendix I.1).

Q5: Failure modes

Can you say something about the failure modes of RuleCast? What would be an example where RuleCast doesn't work well? Are there specific patterns we should expect it has problems with?

On Reddit, RuleCast gains 5.36 MRR points over CRAFT, but AP and ROC-AUC fall by 0.12 and 0.24 points (Tables 1–2). Section 6 also gives a tie case: without the identity residual, candidates with identical behavioral states, pair features, and masks tie for a fixed source and time. Sparse histories leave few past partners for forecasting and little evidence to distinguish candidates. A prior for nodes with little history could use node attributes when available.

Other revisions. Figure 1 is now cited before Figure 2, and Section 3 defines MM as the number of experts when it introduces the expert set.

Thank you for your answers, which helped me better understand some aspects of your work. I appreciate your efforts to address my concerns, for example, by returning to the research questions in the text and adding another paragraph to the conclusion, which is why I am raising my score.

However, I believe the paper would benefit from a more thorough revision to improve clarity and better integrate the new content into a coherent story.

AuthorsOpenReview ↗

Response to Reviewer kFAz (Follow-up on clarity and how the evidence fits together)

Thank you for reading the revision and pointing out that the new material needed to fit more clearly into the paper's argument. We revised the text so that the same question guides the model and the analysis: what can we predict once for the source, and what must we check separately for each candidate?

How we introduce the model (W1). The Introduction now states the distinction before giving examples. The source's past partners inform a forecast of what kind of partner is likely to come next. All candidates for that source and time share the forecast. Sections 4.2–4.3 then distinguish the forecast from a candidate's own current role and explain how role fit, history matching, and pair evidence enter the score. Section 4.4 refers to Figure 2 after defining the score, so the diagram brings together the quantities the reader has just seen.

How each experiment answers a question (W2 and Q3). Section 5 moves from overall benchmark performance (RQ1) to what the forecasting design contributes (RQ2) and when learned routing helps (RQ3). For RQ2, Table 7 asks how RuleCast compares with direct feature scoring. Table 8 separates two questions: State-only removes the past-partner sequence while retaining the current source state, and Simplex versus Continuous compares ways of representing the forecast and scoring its match to a candidate. The two matched representations give close MRR on UCI and LastFM. With role distributions, we can also see which learned roles contribute to the match before other evidence is combined.

For RQ3, Section 5.4 follows the order of scoring: it first uses Figure 3 to ask whether realized partners fit the forecast better than sampled candidates, then examines how the router weights the available evidence. Figure 4 asks a different question: does learning those weights improve ranking relative to uniform weights? The clearest gain on Flights is about 2.0 MRR points for new partners. The text now points from Figure 4 to Appendix I.2, where the new Figure 7 shows the corresponding comparisons on LastFM, YouTube, and MOOC.

What changes when we mask evidence (Q4). Table 9 (Appendix I.1) fixes the checkpoint and candidate lists, then masks expert groups at inference. The rows below show the comparisons discussed in our first response. Values are test MRR (%). Every setting retains the role expert and identity residual; Pair groups repetition, reciprocity, and periodicity.

DatasetEvidence for the true partnerQueriesRole+History+PairFull
FlightsHistory and pair3,59284.3284.3998.3898.53
WikipediaHistory and pair3,68056.5446.8699.8399.86
WikipediaHistory only27026.3428.6026.3428.60

When both evidence types are available for the true partner, adding history to Role + Pair raises MRR by 0.15 points on Flights and 0.03 on Wikipedia. In Wikipedia's history-only stratum, adding history to Role raises MRR from 26.34 to 28.60. This comparison helps explain what history evidence can add while the role forecast stays fixed.

We now link this experiment to Proposition 3 in Appendix E. The proposition gives the exact change in a candidate's score when a group of experts is masked and the remaining weights are renormalized. If the original score gap exceeds the bound on how much it can shrink, the two candidates keep their order. This explains why changes in the evidence scores can affect some rankings and leave others unchanged.

What this means for the model (W3 and Q5). Section 6 returns to a concrete example: two candidates can fit the same forecast equally well, but a prior interaction with one of them can help distinguish them. When the source has little history and the candidates have similar behavior and no pair evidence, there is less information to separate them. Appendix J illustrates this distinction for one source: it traces how the forecast changes and compares the weighted expert terms for the realized partner and a high-scoring sampled alternative at selected times. The conclusion returns to the same idea: predict the kind of partner first, then use the available evidence to rank individual candidates.

Reviewer_r6CmOpenReview ↗
Rating
2
Confidence
3
Informativeness
2
Presentation
2
Soundness
2
Read review
Paper summary

The paper proposes RuleCast for temporal link prediction. The method predicts the behavioral role of the next interaction partner and combines this forecast with candidate-specific historical evidence. A masked router combines experts for role compatibility, history matching, repetition, reciprocity, and periodicity.

Critical strengths
  1. The model explicitly separates the expected behavior of the next partner from candidate-specific historical evidance.
  2. evaluation covers 10 datasets from various domains.
Critical weaknesses
  1. The methodological novelty appears limited. RuleCase combines hand-designed temporal statistics, a GRU, and a masked mixture of experts. Given prior expert-based link predictors such as Link-MoE and ESSEN, the claim of a fundamentally different paradigm needs clearer technical justification.
  2. The interpretation as role forecasting is not sufficiently estabilished. d_u(t) and p_v(t) are jointly learned using link-ranking objectives, and their inner product provides a compatibility score. It is unclear what is gained specifically from representing these vectors as role distributions.
Questions for authors
  1. What specific tech advance distinguishses RuleCast from existing expert-based link predictors beyond the chosen behavior features and expert-availability masks?
  2. Can you compare against a model using the same behavior features, GRU, and experts, but ordinary embeddings instead of role distributions?
2 comments
AuthorsOpenReview ↗

Response to Reviewer r6Cm

Thank you for the comparison with prior work and for suggesting the continuous embedding control.

W1/Q1: Technical distinction from Link-MoE and ESSEN

The methodological novelty appears limited. RuleCase combines hand-designed temporal statistics, a GRU, and a masked mixture of experts. Given prior expert-based link predictors such as Link-MoE and ESSEN, the claim of a fundamentally different paradigm needs clearer technical justification.

What specific tech advance distinguishses RuleCast from existing expert-based link predictors beyond the chosen behavior features and expert-availability masks?

Thank you for asking us to clarify where history enters the model. The distinction is what we derive from history before scoring any candidate. Link-MoE uses pairwise features to route static node pairs among GNN link predictors. ESSEN uses entropy and temperature features of observed and virtual graphs to weight temporal experts.

RuleCast first forecasts a distribution over the next partner's behavior from the source's past partners. It then matches every candidate to that same forecast and scores the evidence available for each pair. This gives all candidates for a source and time the same reference point and lets us examine the forecast separately from pair evidence.

In the revision: Introduction, Section 2, and Figure 2.

W2: What role distributions represent

The interpretation as role forecasting is not sufficiently estabilished. du(t)d_u(t) and pv(t)p_v(t) are jointly learned using link-ranking objectives, and their inner product provides a compatibility score. It is unclear what is gained specifically from representing these vectors as role distributions.

The role distributions give source demand and candidate behavior a common, time-varying representation. Demand specifies how much mass the source places on each role for its next partner; the candidate distribution describes its current behavior in the same coordinates. Their dot product is the probability that independent draws select the same coordinate. This makes it possible to check the forecast before mixing it with pair evidence. On Flights, realized partners have higher mean overlap than sampled candidates in every demand-confidence quartile (Figure 3). This supports the use of overlap as a predictive signal in the learned role space.

In the revision: Sections 4.2 and 5.4, and Figure 3.

Q2: Continuous embedding control

Can you compare against a model using the same behavior features, GRU, and experts, but ordinary embeddings instead of role distributions?

Thank you for suggesting this control. We added a continuous variant that keeps the behavior features, source sequence encoder, and candidate scoring architecture, but replaces log role overlap with scaled cosine similarity. We disable role regularization in both controls and match parameter counts on UCI and LastFM. The simplex leads by 0.09 MRR points on UCI and trails by 0.05 on LastFM. Separately, removing the partner sequence from the demand encoder lowers MRR by 0.10 and 0.16 points, respectively.

In the revision: Section 5.3 and Appendix H.1, Table 8.

AuthorsOpenReview ↗

Response to Reviewer r6Cm (Supplementary Note)

Thank you for suggesting the continuous representation control (Q2). As a brief supplement to our response, we reproduce Table 8 from Appendix H for easy reference. Entries are test MRR (%) as mean ± standard deviation over three seeds.

DatasetRuleCastSimplexContinuousState-only
UCI86.65 ± 0.1086.56 ± 0.0986.47 ± 0.0786.55 ± 0.08
LastFM91.39 ± 0.1591.26 ± 0.0591.31 ± 0.2491.23 ± 0.10
Wikipedia92.19 ± 0.1492.07 ± 0.0292.02 ± 0.0192.09 ± 0.04
Reddit94.69 ± 0.0394.70 ± 0.0494.54 ± 0.0394.57 ± 0.00
Flights91.37 ± 0.1091.16 ± 0.4591.37 ± 0.1891.33 ± 0.01

Simplex and Continuous keep the behavior inputs, source sequence encoder, and candidate scoring architecture. Both disable role regularization; Continuous uses scaled cosine similarity in place of log role overlap. With matched parameter counts on UCI and LastFM, the two differ by at most 0.09 MRR points. State-only answers a separate question: keeping the current source state but removing the past-partner sequence reduces MRR by 0.10 on UCI and 0.16 on LastFM relative to full RuleCast.

To connect this result to W1 and W2, we now introduce the shared forecast before discussing candidate evidence in the Introduction and Sections 4.2–4.3. The technical distinction is that we predict one next-partner role distribution for each source and query time, then compare all candidates in that shared role space. The representation makes those comparisons inspectable even when the ranking accuracy of the two representations is close. Figure 3 shows that realized partners have higher mean role overlap than sampled candidates in every demand-confidence quartile on Flights, before candidate evidence is combined.

Reviewer_BcLuOpenReview ↗
Rating
2
Confidence
3
Informativeness
2
Presentation
2
Soundness
3
Read review
Paper summary

This paper proposes a method for temporal link prediction, and is motivated by the insight that, for predicting a target node for a source, the likely candidates depend on certain behavior roles of previously linked nodes of the source including how they resemble previous partners of the source node, further supported by repetition, reciprocity and periodicity. The authors argue that modelling these statistics separately for every source-candidate pair is better than an implicit singular compatibility function based on node histories alone. To that end, they hand craft nine behavior and role features based on history of a source in query and all candidates and use a learned MLP to obtain a representation for each node, then use a cross attention-based scoring for every candidate - source node pair. The authors validate their approach using popular temporal link prediction benchmarks and baselines include a variety of methods from feature engineered to neural methods. Experiments show the improved benefits of their approach with significant gains in MRR across benchmarks.

Critical strengths
  1. The method proposed is intuitive and motivated well. The featurization decomposition also allows a practitioner to diagnose / interpret using behavior roles.

  2. The experimental evals show consistent gains for the method proposed across datasets. and in comparison, to popular and apt baselines.

Critical weaknesses
  1. The central claim in the paper that forecasting partner roles and candidate grounding are mutually exclusive. But in the experiments, simpler ablation of feature mlp vs RuleCast only shows very minor gains in MRR. So, the question of role protocol factorization and mechanism experts that are dynamically selected are they needed ?

  2. For Table 1,2, only CRAFT has been reproduced on the same splits, available histories, candidate counts, negatives, and tie handling, are the same experiment protocol used for the other baselines like TGN , CAWN TGAT, etc ? If not then the experimental results are not apples - to - apples which weakens the argument of the paper and method proposed.

Questions for authors

Please see the second question in weakness.

3 comments
AuthorsOpenReview ↗

Response to Reviewer BcLu

Thank you for your careful reading and for asking us to clarify the role of the model components and the baseline comparison.

W1: Role factorization and learned routing

The central claim in the paper that forecasting partner roles and candidate grounding are mutually exclusive. But in the experiments, simpler ablation of feature mlp vs RuleCast only shows very minor gains in MRR. So, the question of role protocol factorization and mechanism experts that are dynamically selected are they needed ?

Partner-role forecasting and candidate grounding work together: the forecast provides a shared reference, and grounding adds evidence for each candidate. RuleCast improves on Feature-MLP by 0.17-0.89 MRR points across the five reported datasets. The larger drop for Role+protocol only shows that role overlap alone leaves out useful candidate evidence.

The factorization also makes the score easier to inspect: Feature-MLP maps its inputs directly to a score, whereas RuleCast lets us compare the shared demand with each candidate's role and examine the available expert scores separately. Figure 8 shows the weighted expert contributions for a realized partner and the highest-scoring sampled negative.

For dynamic routing, we distinguish expert availability from expert weighting. The mask makes it explicit which evidence can enter a candidate's score. The router then weights only those supported experts, and Figure 3 shows how its allocation changes with the available evidence. Uniform routing keeps the same masks, so it tests the value of learning the weights. The learned router adds 0.05-0.43 MRR points overall across the four datasets and about 2.0 points for new partners on Flights, with little change in the recurring-evidence strata.

In the revision: Sections 5.3–5.4, Table 3, Figures 3–4, and Appendices H and J (Figure 8).

W2/Q1: Baseline evaluation protocol

For Table 1,2, only CRAFT has been reproduced on the same splits, available histories, candidate counts, negatives, and tie handling, are the same experiment protocol used for the other baselines like TGN , CAWN TGAT, etc ? If not then the experimental results are not apples - to - apples which weakens the argument of the paper and method proposed.

Please see the second question in weakness.

Thank you for asking us to clarify the comparison. RuleCast and the baselines in Table 1 follow the same evaluation protocol for each dataset. Section 5.2 lists the common settings, and Appendix K gives the dataset-specific splits and sampling rules.

In the revision: Section 5.2, Tables 1–2, and Appendices F and K.

AuthorsOpenReview ↗

Response to Reviewer BcLu (Supplementary Note)

Thank you for asking what the role forecast and candidate-specific evidence each contribute (W1). As a brief supplement to our response, we include the relevant table entries and summarize the new evidence-stratified analysis. The tables report test MRR (%) as mean ± standard deviation over three seeds.

Direct feature scoring (Table 7 and Appendix H). Feature-MLP uses the behavior and pair features to score candidates directly. RuleCast ranks higher on all five reported datasets, with gains of 0.17–0.89 MRR points.

DatasetFeature-MLPRuleCast
Wikipedia91.92 ± 0.0092.19 ± 0.14
UCI86.29 ± 0.3086.65 ± 0.10
LastFM91.05 ± 0.0491.39 ± 0.15
Flights90.48 ± 0.0491.37 ± 0.10
Reddit94.52 ± 0.0194.69 ± 0.03

Candidate evidence and routing (Table 3, excerpt). Role+protocol only retains the role score without the other experts or the identity residual. Uniform router keeps the same expert availability rules and assigns equal weights to the supported experts. These controls ask different questions: how far the role score alone can rank candidates, and what learning the mixture weights adds when the available expert types are held fixed.

VariantWikipediaUCILastFMFlights
Role+protocol only64.41 ± 3.5960.43 ± 0.1938.30 ± 0.1859.56 ± 0.01
Uniform router92.06 ± 0.0086.60 ± 0.1190.96 ± 0.0191.11 ± 0.12
RuleCast92.19 ± 0.1486.65 ± 0.1091.39 ± 0.1591.37 ± 0.10

We also added Figure 7 in Appendix I.2 to show how the routing gains vary by evidence type. In this paired evaluation of seed-0 checkpoints, learned routing adds about 0.35 MRR points on repeated LastFM pairs and 0.86 on new YouTube partners. On MOOC, it adds 13.23–19.44 points across the observed strata. The revised Section 5.4 distinguishes the ranking changes from the router allocations in Figure 3: one measures ranking, and the other shows how the model distributes weight among supported experts.

Thanks to the authors for the rebuttal and additional discussion and experiments. Appreciate them for addressing some of the questions raised in the review In light of other reviews and related discussions I do feel that the paper in the current form is not yet fully ready for acceptance. The main weakness on feature mlp vs RuleCast showing very minor gains in MRR. still holds even with the newer experiments performed during rebuttal. So, the question of the need for role protocol factorization and mechanism experts stands. Thanks to authors again for engaging in the rebuttal period.

Comments on the paper

1 comment
AuthorsOpenReview ↗

Official Comment by Authors

We thank all reviewers for their careful reading and constructive feedback. Their questions helped us clarify the motivation and presentation of RuleCast, strengthen the comparison with direct scoring and continuous representations, and better connect the analyses to our modeling approach. We appreciate the time and effort the reviewers and area chair have devoted to the discussion.

From OpenReview, CC BY 4.0. Authors as signed there; shown unedited.

Related papers

Loading the map…

Discussion (0)

Sign in to comment.