-
Notifications
You must be signed in to change notification settings - Fork 95
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
relation matching #1
Comments
Yes we will provide soon, along with the data and instructions. |
@apoorvumang When do you provide data and instructions? |
@IISCAditayTripathi OK, Thanks. |
Hi, @apoorvumang thanks for providing these useful codes and instructions. |
Hi @Kelaxon That is a typo. It should be same as in section 4.4 ie a' \in E. We were earlier experimenting with restricting the neighbourhood, which was denoted by N_h, but the final version of EmbedKGQA does not have that restriction. |
@apoorvumang Thanks for your reply. Yes, I found the restricting neighborhood part in |
@apoorvumang When do you provide relation matching code?It's nine months since you said public code last time.I'm very curious about the implementation of relation matching |
@RainbowRr Apologies, I have been busy with some other work and sidelining this for way too long. Please keep posted on this thread I will add the implementation in some form or another within the next 3 days. |
Thank you very much! Wish you success in your work and research! |
@RainbowRr I have added the code. Please let me know if you face any issues |
You will need to re-download the data and pretrained_models |
Closing for now, please reopen a new issue if you have problems with the implementation |
Thanks for opening source !
I have read the code, but I did not find the relation matching module. The current prediction logic seems to be predicting scores for all entities of KG. Will you provide the code for relation matching, because I am not sure how is the shortest path between head entity and candidate answer defined.
The text was updated successfully, but these errors were encountered: