How are you solving for PDFs that are too large to fit in the token context? I know of a few approaches for that: - Ignore the problem and let it hallucinate answers to anything that's not in the first 5-10 pages - Attempt to recursively summarize the PDF at the start - so summarize e.g. pages 1-3, then 4-6 etc, then if the resulting summaries are still too long for the context window run a summary of those summaries…
The FAQ answers my question: > In the analyzing step, ChatPDF creates a semantic index over all paragraphs of the PDF. When answering a question, ChatPDF finds the most relevant parapgrahs from the PDF and uses the ChatGPT API from OpenAI to generate an answer. Are you using OpenAI's embeddings to implement that?
For a simple example, a car manual where you want to change the brakes, it probably won't tell you in the brake section how to remove the wheels. You have to look at the wheel section. And in the wheel section it won't tell you about the nuts, you have to look in the spec sheets. And the spec sheet won't have the torque, you have to look in the chapter reference.
Often times they are not nice enough to point you to the relevant sections, you just have to stumble around the manual for a long time.