Knowledge-Graphs

Memory is where many impressive agents quietly become mediocre employees. They can answer the last question. They can summarize the last document. They can sound very confident about a customer, a project, or a workflow they saw three weeks ago. Then someone asks, “Why did we make that decision?”, “When did the requirement change?”, or “Was that the same client who objected last time?” Suddenly the agent rummages through its past like a consultant searching Slack at 1:43 a.m. Technically alive. Not exactly organized. ...

Search used to be a polite negotiation with a database. You typed keywords. The system returned papers. You inspected titles, opened tabs, skimmed abstracts, cursed quietly, adjusted the keywords, and repeated the ritual until either the literature became clear or your soul left the building. Large language models changed the ritual, but not always for the better. Now a system can answer a research question directly, which feels magical until one remembers that “fluent” and “correct” are not synonyms. In scholarly work, this distinction is not academic decoration. It is the difference between literature discovery and very confident misinformation wearing a lab coat. ...

Greenwashing usually begins with a sentence that sounds harmless enough. “We reduced emissions.” “Our operations are greener.” “This product supports a sustainable future.” Very nice. Also very convenient. The problem is that none of these claims can be judged by grammatical confidence, public relations polish, or the warm glow of the word sustainable. A serious reviewer has to ask uglier questions: reduced compared with what year? Which scope of emissions? Which facility? Which product line? Is the claim about a target, an initiative, or actual measured performance? ...

Deletion sounds simple until the system still knows the thing you deleted. A company removes a sensitive supplier label from its knowledge graph. A hospital publishes a subset of a medical ontology without exposing internal diagnostic codes. A compliance team rewrites a rule base so external partners can query it without seeing the original vocabulary. Everyone nods. The data is “sanitized.” The schema is “simplified.” The private terms are gone. ...

Maps are useful because they are not the territory. Nobody opens Google Maps and assumes the blue line has physically repaired the road. Sensible people use it to orient themselves, notice routes, avoid obvious mistakes, and decide where to inspect more carefully. That is the cleanest way to read DEMOCRITUS, the system described in Large Causal Models from Large Language Models.1 It does not make LLMs magically perform causal inference. It does not estimate treatment effects. It does not solve confounding. It does not turn a pile of text into scientific truth by sprinkling geometry on top, though that would be a very efficient way to sell consulting decks to executives with poor impulse control. ...

Memory, Multiplied: Why LLM Agents Need More Than Bigger Brains Memory is where many AI demos go to die. The demo looks fluent. The agent remembers the last three messages, calls a tool, summarizes a PDF, maybe even smiles politely while destroying your calendar. Then you return tomorrow and ask it to continue a project involving a client, two documents, three images, and a corrected assumption from last week. Suddenly the “agent” becomes a very expensive intern with amnesia. ...

Map distance is not truth. Anyone who has followed a GPS into a dead-end road knows this already. But distance is still useful. If a restaurant is 300 meters away, it is usually a more plausible lunch option than one across the ocean. If a customer record links directly to an invoice, and that invoice links directly to a shipment, the shipment is a more plausible grounding for a customer-service question than a random supplier buried in another region’s procurement graph. Not guaranteed. Just plausible. That small distinction is where the paper becomes interesting. ...

Captioning looks easy until the caption has to be true. A consumer image captioning model can say, “a man standing at a podium,” and most people will nod. A newsroom cannot stop there. It needs to know whether the man is a senator, a witness, a CEO, a defendant, or simply someone unlucky enough to stand near a microphone. It may need the committee name, the location, the event, the year, the organization behind the banner, and the person half-visible at the edge of the frame. Journalism, as usual, ruins the demo. ...

A scientist does not usually fail because they cannot ask the right question. More often, they fail because the useful answer is buried behind five separate systems: a biomedical knowledge graph, a disease-module algorithm, a drug-prioritization method, a literature database, and a visualization tool that looks innocent until someone has to configure it. ...

The camera saw something. The caption invented the rest. A vision-language model looks at a landmark and produces a caption. The caption is fluent. The architecture sounds plausible. The location sounds authoritative. The historical detail has just enough specificity to discourage questions. And that is the problem. In many business settings, a wrong visual description is not wrong in the theatrical way people imagine when they hear “AI hallucination.” It is not a neon giraffe in a board meeting. It is a product listed under the wrong category. A heritage photo tagged with the wrong site. A compliance image described with an unsupported claim. A training material that quietly teaches a false relationship between a place, an object, and its context. ...