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

why gpt-4 could change the vector search keywords in the second conversation , by other LLM model can not do this #1759

Closed
2 tasks done
xutengfei opened this issue Dec 15, 2023 · 3 comments
Assignees
Labels
🙏 help wanted Extra attention is needed

Comments

@xutengfei
Copy link

Self Checks

Dify version

0.3.32

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

why gpt-4 could change the vector search keywords in the second conversation, by other LLM model could not chang the keyword(use whatever that user input)
image
image

✔️ Expected Behavior

change the keywords to right intention of user, not the user input

❌ Actual Behavior

search vector with whatever user typed in the second conversation

@xutengfei xutengfei added the 🐞 bug Something isn't working label Dec 15, 2023
@crazywoola crazywoola added 🙏 help wanted Extra attention is needed and removed 🐞 bug Something isn't working labels Dec 15, 2023
@guchenhe
Copy link
Collaborator

Hi there,

could you provide more info, like embedding model and prompt used?

@xutengfei
Copy link
Author

Hi there,

could you provide more info, like embedding model and prompt used?

prompt: you are an analyst ,you will give a report about {{input}}
embedding : text2vec
LLM: baichuan\chatglm\gpt4

Copy link

dosubot bot commented Mar 29, 2024

Hi, @xutengfei

I'm helping the team manage their backlog and am marking this issue as stale. From what I understand, you opened this issue regarding the behavior of GPT-4 in changing vector search keywords in the second conversation. There was a request for more information such as the embedding model and prompt used, to which you responded with the details.

Could you please confirm if this issue is still relevant to the latest version of the repository? If it is, kindly let the team know by commenting on the issue. Otherwise, feel free to close the issue yourself, or it will be automatically closed in 7 days. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🙏 help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

4 participants