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

Weird behavior of AI search service #458

Open
rochaktarika123 opened this issue Dec 15, 2023 · 3 comments
Open

Weird behavior of AI search service #458

rochaktarika123 opened this issue Dec 15, 2023 · 3 comments
Labels

Comments

@rochaktarika123
Copy link

We have implemented this application which leverages internal documentation if it can find an answer else it provides from the pre-trained GPT datasets.
I am seeing some weird behavior that if the user asks a question on the internal documentation, the app works well and can give answers but if the user asks the first question very generic like "Who is XYZ celebrity" or even a greeting "hello", that the application has to find an answer from the pre-trained datasets, it is not able to answer any further questions based on the internal documentation then.
I have tried to modify the configuration parameters like temperature, top_p, or even the system prompt but the behavior is still there.

Any idea why is this happening?

@QuentinAd
Copy link

QuentinAd commented Dec 19, 2023

I have seen similar behavior. When looking at the logs in debug mode, I have seen that the Azure Search AI citations are being added to the OpenAI request in the citations (in role: tool). However for some reason it is not citing or saying the information is not there even when I see the citation added to the request.

I have seen similar behavior when not the first questions, sometimes also other questions down the conversation.

@sarah-widder
Copy link
Contributor

Hi @rochaktarika123 you might try adjusting the 'inScope' parameter, or strictness. Turning off 'inScope' or reducing the strictness value will make the model more likely to answer outside of the internal documentation data.

Copy link

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Dec 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants