Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Early stopping with numeric edge values #253

Open
AlejandroTL opened this issue Jun 17, 2021 · 2 comments
Open

Early stopping with numeric edge values #253

AlejandroTL opened this issue Jun 17, 2021 · 2 comments

Comments

@AlejandroTL
Copy link

Hello!

Is there any way to specify in the early stopping parameters the numeric edge values of the validation test? I'm trying to do it but I cannot find where to place the numeric edge values of my validation set. If not, what should be the path to implement early stopping with numeric values on the edges? Manually?

Thank you, awesome library!

@sumitpai
Copy link
Contributor

During the test/valid time, we don't specify the numeric values. Instead, what we would expect is that when a triple has a high numeric value, when ranked against all corruptions, the triple should get a good rank; while a triple with a low numeric value MIGHT probably be noise, and you can expect it to be ranked lower. This needs to be done manually.

For validation in specific, we can train the model to early stop if it does good on high valued triples (i.e. you can pass only high valued triples to early stopping paramter x_valid and early stop on mrr criteria)

@sumitpai
Copy link
Contributor

The numeric values are mainly used during training to focus the models on high valued triples over the low valued ones. At test time one can split the test set into 2 parts (as done in paper) and see if models performs good on these 2 sets using the delta mrr metric

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants