Skip to content
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

feat (example): Add Ollama Retrieval Example #1051

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

hcmlinj
Copy link

@hcmlinj hcmlinj commented Oct 20, 2024

Background

Providing specific information or domain knowledge ensures that the AI gives priority to this when responding.
The main questions we will ask are "What is this?" If there is direct relevance, prioritize answering based on the information we provided. Otherwise, simply respond without referencing our information, and avoid mentioning the provided details unless necessary.
When asking the AI a question, we expect foo and f4 to be answered based on the information we provided.
When asking about foodpanda and panda, we expect the AI to respond based on its own knowledge.

Testing

This is an example executed on my laptop.

#2 foo
9527

#1 foodpanda
Foodpanda is an online food delivery service platform. It allows users to order food from various restaurants in their area and have it delivered to their doorstep.

#3 f4
F4 refers to a Taiwanese boy band that was formed in 2001 after the success of the Taiwanese drama Meteor Garden, where they starred.

#4 panda
Panda is a type of bear native to China. It is known for its black and white fur. The term "panda" is not directly related to the provided context about Foo or F4.

PR Checklist

  • Read the Contributing documentation.
  • Read the Code of conduct documentation.
  • Name your Pull Request title clearly, concisely, and prefixed with the name of the primarily affected package you changed according to Good commit messages (such as memory: add interfaces for X, Y or util: add whizzbang helpers).
  • Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
  • Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. Fixes #123).
  • Describes the source of new concepts.
  • References existing implementations as appropriate.
  • Contains test coverage for new functions.
  • Passes all golangci-lint checks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant