Global temporal and leave-last-out splitting for next-item evaluation#708
Open
hieuddo wants to merge 4 commits into
Open
Global temporal and leave-last-out splitting for next-item evaluation#708hieuddo wants to merge 4 commits into
hieuddo wants to merge 4 commits into
Conversation
Member
Author
|
Quick runs (10 epochs) with Beauty:
Sports:
Toys:
|
lthoang
reviewed
Jul 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The current
NextItemEvaluationonly supports pre-split data viafrom_splitswith three datasets:Diginetica,RetailRocket, andCosmetics; already preprocessed and uploaded in bundle train/val/test. We should move to more transparent data loading/splitting. Recent studies have also shown some flaws/issues in data splitting that lead to data leakage:This PR adds:
NextItemEvaluation.from_timestamps: a global temporal split, the leakage-free protocol recommended by [2], similar to the existingTimestampSplitfor rating data.NextItemEvaluation.leave_last_out: the per-user leave-one-out split, commonly used in the sequential literature. We'll raise a warning that this splitting method leaks cross-user future information; we support this because it is still very common.SequentialDataset.build: warns when rows within a session are not chronological.amazon_reviewdatasets:Beauty,Sports_and_Outdoors, andToys_and_Games; which are widely used in Semantic ID papers. For now, we only implementload_feedbackto use these three as normal rating data. Anyload_textorload_item_metadataare for future implementation with some Semantic ID models (e.g., TIGER, RQ-VAE).Related Issues
Checklist:
datasets/README.md(if you are adding a new dataset).