We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
I can print the sparql from https://github.com/UKP-SQuARE/square-core/tree/master/skills/kgqa-kqapro in the UI if it's always returned. To do this, we would need to update the API schema though... and it's getting a bit bulky
Is showing the sparql actually useful? I would indeed help for explainability though
afaik, right now sparql is not only shown for syntax errors in the sparql
The text was updated successfully, but these errors were encountered:
Currently, SPARQL will only be shown when it cant get the answer from back-end KG. This could be caused by two reasons:
I agree showing SPARQL would be helpful for explainability. Do we need to change the prediction constructor to make it work?
Sorry, something went wrong.
yes, I think we would need to change the prediction construction, but @timbmg may give a better answer
timbmg
HaishuoFang
No branches or pull requests
Hi,
I can print the sparql from https://github.com/UKP-SQuARE/square-core/tree/master/skills/kgqa-kqapro in the UI if it's always returned. To do this, we would need to update the API schema though... and it's getting a bit bulky
Is showing the sparql actually useful? I would indeed help for explainability though
afaik, right now sparql is not only shown for syntax errors in the sparql
The text was updated successfully, but these errors were encountered: