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

[Issue]: Incorrect answer by local query. Referenced wrong entinties #862

Closed
2 tasks done
KylinMountain opened this issue Aug 8, 2024 · 1 comment
Closed
2 tasks done
Labels
awaiting_response Maintainers or community have suggested solutions or requested info, awaiting filer response

Comments

@KylinMountain
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues
  • I have checked #657 to validate if my issue is covered by community support

Describe the issue

I have a query like Person A is actively compensated the other party?

But it matched to another person B and compensates.

In the data, there’s no accident occurred in person A case. Only person B has actively compensates the other party.

ps there’s entity type like person and compensated.

So how do we optimize such query? The entity person should have more priority, it should look up person an and then get its compensates.

Steps to reproduce

No response

GraphRAG Config Used

# Paste your config here

Logs and screenshots

No response

Additional Information

  • GraphRAG Version:
  • Operating System:
  • Python Version:
  • Related Issues:
@KylinMountain KylinMountain added the triage Default label assignment, indicates new issue needs reviewed by a maintainer label Aug 8, 2024
@natoverse
Copy link
Collaborator

This sounds like it may be a hallucination issue? It sounds like the nature of your domain requires some prioritization that isn't present in the default prompts.

I put some comments here about tuning query prompts: #917. It's a little bit of work at the moment, but hopefully can be config driven soon.

@natoverse natoverse added awaiting_response Maintainers or community have suggested solutions or requested info, awaiting filer response and removed triage Default label assignment, indicates new issue needs reviewed by a maintainer labels Aug 16, 2024
@natoverse natoverse closed this as not planned Won't fix, can't repro, duplicate, stale Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting_response Maintainers or community have suggested solutions or requested info, awaiting filer response
Projects
None yet
Development

No branches or pull requests

2 participants