Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR addresses #38 and #45 to some extent.
Here is how the implementation works currently:
I have made use of neo4j graph database and this is how the visualization looks there:

This is how the current Streamlit representation looks like:

Chatbot functionality questions example:

This is how the chatbot query would work:
Note:
Please create a neo4j cloud/aura instance and add these 3 fields in your .env file for the graph implementation part:
Improvements:
Query 1: I used the word "education" in my query and since there is a education node in our neo4j graph, the chatbot could provide relevant response:
Query 2: I used the word "studied" in my query, but chatbot fails to respond because it could not correlate education & studied

oops! actually this time it did work but still keeping a note of this if at all a similar issue occurs again. We may need to change our prompt to tackle this I guess? Or maybe change the model? Let me know if there are any other ways please