What about splitting bigger content into chunks before embedding?

freakynit 2 hours ago | parent | next [-]

How are you gonna handle the relations that span across individual chunks... if a later chunk refers something from 2 chunks before using `it`, rather than proper name, how will you handle that? Because at query time, that later chunk would not match.

	▲	gf000 a minute ago \| parent \| next [-]
		Absolutely a novice in this topic, but I would imagine that by simply having sufficiently big chunks it's simply not a problem? You surely have enough information in like a couple of paragraphs to denote in vector space roughly what it is about. So that both chunks would get found by a vector search, and then whatever is the logic it may put the whole original text of those chunks into context, but in any case enough so that an LLM can "reason" about the references in-between the two.
	▲	refactor_master 12 minutes ago \| parent \| prev [-]
		Humans usually have ways around that in longer documents eg page numbers, paragraphs, links. If someone gave me a report, in my hands, that said “see ‘it’” I’d also be confused.

▲

mdp2021 37 minutes ago | parent | prev [-]

What member freakynit said nearby about chunks and relations between chunks, plus the storage and information efficiency problem: make some calculations about storing vectors - for paragraphs and for collections of paragraphs -, then compare the needed space with the original data...

Because you could have clever ideas about vectors related to more paragraphs related in the document structure - but that would multiply the vectors. The index can become much bigger than the corpus.