-
Notifications
You must be signed in to change notification settings - Fork 20
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
Question about the tail re unit #8
Comments
Part of the reason is in the justification part of readme.md in pfn-nested folder. Also, since head to head and tail to tail are coming for different results, using the same feature might not be optimal. Empirically speaking, switching them leads to faster convergence In our experiment. So we stick with this formula. |
Thank you for your prompt response. In terms of best performance, is there a significant difference between the two settings? And if yes, can you please elaborate? |
Here is the thing, industry people used pfn on their Chinese dataset and the result is super low because there are so many head-overlap triples in their dataset. so I provided them with pfn-nested, the result got normal under pfn-nested. All in all, pfn-nested is designed mainly to cover the issue of nested triple prediction. As for performance in current dataset, I only used it on scierc, the result is displayed in the main page though. I did try to use it on ace05, but I ran into oom error with batch size 20. There is no systematic evaluation of pfn-nested though, you can verify the performance yourself if you’re interested. |
Thank you. This answers my questions. |
And by the way, this work is indeed truly impressive. Best wishes on further explorations! |
ok, thanks a lot. |
Is there a reason why the order of h_re and h_share are swapped here as compared to over here ?
Thanks for any help.
The text was updated successfully, but these errors were encountered: