Contrastive Learning

Most document AI still behaves like a very diligent librarian with one bad habit: it files things by subject even when the useful question is about function. A customer support message about a refund, a legal paragraph about a breach, and a sales call transcript about price resistance may share almost no vocabulary. Standard embeddings will usually respect that difference. Finance goes with finance, legal goes with legal, complaints go with complaints. Neat shelves. Terrible diagnosis. ...

Symbols are easy to digitize and surprisingly hard to respect. A business team sees two product names, two supplier records, two compliance clauses, or two scanned forms that look related. The lazy engineering answer is: “label the matches, label the non-matches, train a contrastive model.” That answer often works. It is also how many embedding systems quietly turn uncertainty into false certainty, then call the result “semantic similarity.” Very tidy. Very confident. Occasionally very wrong. ...

Search systems fail in boring ways before they fail in spectacular ones. A customer uploads a product photo and receives visually similar items that miss the actual intent. A compliance analyst searches a scanned document and gets pages that look close but answer the wrong question. A visual QA system finds the right region but ranks the wrong evidence first. Nobody in the meeting says, “Ah yes, our embedding space has poor spectral noise allocation.” They say the search feels unreliable. Much more executive-friendly. Much less useful. ...

TL;DR for operators The paper behind THEME is not really about asking an LLM to “find AI stocks” and hoping it returns a genius portfolio, because that would be the usual theatre with a Bloomberg terminal costume.1 It is about building a retrieval layer that understands investment themes as a special kind of search problem: cross-sector, text-heavy, time-sensitive, and annoyingly allergic to static classification. ...