[GH-ISSUE #4556] Poor results with embedding of documents #2895

Closed
opened 2026-02-22 18:31:43 -05:00 by yindo · 1 comment
Owner

Originally created by @thomasbrunner-spec on GitHub (Oct 17, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4556

Dear Community,

I use AnythingLLM with ollam and the following models on a Mac:
gpt-oss120:b
Qwen3-Embedding-8B:F16

Chunking 1000, overlap 100

When I upload a document (PDF) into my workspace (example 10 pages), it seem that significant information is missing. Acutally it is a contract to be analysed and it contains regulations for termination. If I prompt to list the regulations during the contract analysis, the answer is that this information can not be found in the document.

Did anybody make similar experiences? How can I fix or improve this issue?

Thanks

Thomas

Originally created by @thomasbrunner-spec on GitHub (Oct 17, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4556 Dear Community, I use AnythingLLM with ollam and the following models on a Mac: gpt-oss120:b Qwen3-Embedding-8B:F16 Chunking 1000, overlap 100 When I upload a document (PDF) into my workspace (example 10 pages), it seem that significant information is missing. Acutally it is a contract to be analysed and it contains regulations for termination. If I prompt to list the regulations during the contract analysis, the answer is that this information can not be found in the document. Did anybody make similar experiences? How can I fix or improve this issue? Thanks Thomas
yindo closed this issue 2026-02-22 18:31:43 -05:00
Author
Owner

@timothycarambat commented on GitHub (Oct 17, 2025):

Embedding uses chunks of the information for semantic retrieval. The downside of this is the semantics do not perform well when you a comprehensive question. For example, regulations may be 3-5 chunks in the entire set. So in this case you might want to increase the # of chunks, or enable reranking, or both to improve retrieval for documents too large to be fully injected.

@timothycarambat commented on GitHub (Oct 17, 2025): Embedding uses chunks of the information for semantic retrieval. The downside of this is the semantics do not perform well when you a _comprehensive_ question. For example, regulations may be 3-5 chunks in the entire set. So in this case you might want to increase the[ # of chunks](https://docs.anythingllm.com/chatting-with-documents/introduction#vector-database-settings--max-context-snippets), or [enable reranking](https://docs.anythingllm.com/chatting-with-documents/introduction#vector-database-settings--search-preference-reranking), or both to improve retrieval for documents too large to be fully injected.
yindo changed title from Poor results with embedding of documents to [GH-ISSUE #4556] Poor results with embedding of documents 2026-06-05 14:49:08 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#2895