Overview
- Paper: Co-LMLM: Continuous-Query Limited Memory Language Models
- arXiv: https://arxiv.org/abs/2607.07707
- Authors: Yair Feldman, Linxi Zhao, Nathan Godey et al. (Cornell, University of Washington)
- Categories: cs.CL, cs.AI, cs.LG
- Knowledge staleness — weights are frozen after training.
- Hallucination — models interpolate in weight space when memory is fuzzy.
- No provenance — models cannot cite the source of a fact.
- Inefficiency — storing Wikipedia (tens of GB) in trillions of parameters is extremely uneconomical.
- A 360M-parameter Co-LMLM, pretrained on Wikipedia and FineWeb-Edu, achieves lower perplexity than a vanilla LLM pretrained on 40x more data.
- On SimpleQA, the 360M Co-LMLM performs on par with GPT-4o-mini and above Claude Sonnet 4.5.
- Updating knowledge by editing text values, no retraining.
- Deleting sensitive facts by removing key-value pairs.
- Restricting sources by controlling which knowledge base subsets the model accesses.
- Auditing answers by inspecting which text spans were retrieved.
Key points
The motivation: knowledge shouldn't live in weights
Conventional LLM pretraining compresses internet text into model weights. This causes well-known problems:
Limited Memory Language Models (LMLMs) flip this: knowledge lives in an external repository, and the model generates queries and composes retrieved text into its answers.
Continuous queries over an unstructured knowledge base
Earlier LMLMs depended on relational knowledge bases (e.g., Wikidata) and structured query languages like SPARQL, requiring pre-curated entity-relation triples.
Co-LMLM's breakthrough: the knowledge base stores continuous vector keys + raw text values, and the model generates a vector query at runtime rather than SQL or keywords:
1. The model reads the current context. 2. It generates a vector query. 3. It retrieves the most similar keys in the knowledge base. 4. The corresponding text values are fused into generation.
Unlike a standard vector database (e.g., Pinecone, Milvus), the keys are generated dynamically by the model rather than precomputed.
Automatic annotation pipeline
Co-LMLM ships with a pipeline that ingests arbitrary text (web pages, papers, novels, chat logs), identifies factual snippets, encodes them as vector keys, and stores them. Knowledge bases can therefore be built from FineWeb-Edu, arXiv, or any text source—no manual structuring required.
Results: small model beats large models
The takeaway: decoupling knowledge storage from reasoning may be key to efficiency—store facts in an optimized database and let the model focus on how to query and use them.
Knowledge control as a built-in capability
Because knowledge is external, Co-LMLM supports:
One-line summary
Co-LMLM teaches models to "look things up smartly" rather than memorize harder—freeing knowledge from weights makes models smaller, more accurate, more controllable, and finally source-aware.