[gigel82]

No. That works for documentation where you do text search and extract paragraphs around the results for "context".

I want it to understand a complete fiction book and tell me about how a character grows throughout their journey from chapter 1 to chapter 12 over 350 pages.

[ElFitz]

Depending on the book you could use that to extract all excerpts where the character appears.

Then each excerpt could be fed to the LLM asking it how this part relates to the question you’d want an answer to.

Then ask for each what it shows about the character and it’s personality, weaknesses, etc.

And finally recursively summarise them, asking for the summary to show how the character has grown through the summarised content.

Basically ending up with a map-reduce.

Bigger sources, or lots of content related to the character, would lead to less accuracy, and increase the likelihood of hitting the window’s limit.

It would also be highly specific and quite brittle, although one could probably turn it into a more generic process / pipeline (ie what dust.tt enables).

I might have completely missed your point or overlooked some glaring flaw though, in which case please do let me know what you think.