-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Gramhagen/wikidata #902
Gramhagen/wikidata #902
Conversation
Check out this pull request on ReviewNB: https://app.reviewnb.com/microsoft/recommenders/pull/902 You'll be able to see notebook diffs and discuss changes. Powered by ReviewNB. |
Thanks a lot @gramhagen ! Very nice to see how you handled the sessions. Maybe we could surface one example of the steps on how to get the Wikidata ID and the Links as different steps, since we query different APIs and some people may want to just use one or another example. Eg: just get the wikidata ID from a text query, or from a wikidata ID get the related entities or description |
Makes sense. We can show the steps in the first example and then use the helper function later. I'll update the notebook. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
weird error in pyspark:
maybe a problem with the spark instantiation? |
Description
clean up to wikidata notebook and utils, this does speed up the notebook execution a bit (first data pull went from 8s -> 5s), the longer movielens data pull should be faster too (also i just clipped it to 50 by default)
@almudenasanz it would be great to get your feedback here. I hid some of the functionality to make it easier to reuse the code, but if you think it's important to surface the functions to get the entities, links, and descriptions we can add that back into the notebook.
Related Issues
#880 it's possible that this might help (mainly due to session caching?) I did limit some of the results in the normal case, but that shouldn't impact the integration test.
Checklist: