Large Language Models

Customer networks are messy. Product graphs are messy. Fraud rings are messy. Supply-chain graphs are messy. The usual engineering reflex is also messy: when the graph model disappoints, add another architecture, another positional encoding, another “graph-aware” module, another clever acronym to the pile. The paper Semantic Refinement with LLMs for Graph Representations suggests a quieter alternative: before changing the model, change what the model is asked to read.1 ...

A contract clause appears in a chatbot response. Not a summary. Not a paraphrase. The clause itself, with the same odd phrasing, the same punctuation, and the same mildly embarrassing typo that legal counsel thought nobody outside the company would ever see. The model did not “reason” its way there. It remembered. ...

A patient says the pain is manageable. The medication chart looks stable. The latest score is not alarming. Then, sometime before the next formal reassessment, the pain breaks through. That is the operational problem behind Zhuang et al.’s study on predicting lung-cancer pain episodes with a hybrid machine-learning and large-language-model pipeline.1 The paper is not really about whether “AI can predict pain,” a sentence that sounds impressive until one remembers that dashboards have been predicting things since before consultants discovered the word “agentic.” The more interesting question is narrower and more useful: when should a hospital trust structured data, and when should it ask a language model to read the messy clinical story around the data? ...

Warehouse. That is a useful place to begin, because combinatorial optimization only sounds abstract until someone has to decide which trucks leave first, which jobs enter which machines, which items fit into which containers, or which solver should be trusted before the deadline starts laughing. In those systems, the hardest question is often not “What is the answer?” It is “Which method should we use for this particular instance?” One algorithm works beautifully on one family of cases and then quietly embarrasses itself on another. This is not a personality flaw. It is the normal condition of optimization. ...

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. ...

Forecasting With a Spine: How Semantic Anchors Might Fix Time-Series LLMs Forecasting looks simple until the spreadsheet starts moving. A retailer wants next month’s demand. A grid operator wants tomorrow’s load. A finance team wants exchange-rate exposure. In each case, the raw material is not language. It is a jagged sequence of numbers: trend, seasonality, shocks, noise, reporting quirks, holiday distortions, and the occasional data pipeline accident wearing a fake moustache. ...

TL;DR for operators A new benchmark does not say that LLMs are hopeless at planning. That would be too easy, and also false. It says something more useful: frontier models are now strong enough to solve many formal planning tasks, but their competence still weakens when the task stops giving them semantically meaningful labels.1 ...

Markets have a talent for embarrassing elegant models. A factor model says a company looks cheap, profitable, revised upward, less volatile, or attractively positioned. A news headline says the company just changed guidance, delayed a merger, won a contract, received a regulatory opinion, or did something else that refuses to fit politely into a spreadsheet. The obvious modern temptation is to feed both into a large language model, add some attention, and let the machine discover alpha. Naturally, because this is finance, the obvious temptation is not quite correct. ...

TL;DR for operators An AI financial assistant may sound balanced, prudent, and numerate. That is not the same thing as being suitable. The paper behind this article tests leading LLMs on 14 financial decision questions and compares their answers with human responses from a cross-national dataset covering 53 nations.1 The models mostly behave like expected-value machines on lottery-style questions. Give them a risky payoff with clear probabilities, and they often land near the mathematically neutral answer. Very tidy. Very spreadsheet. Very unlike the way many actual clients think when money is uncertain and losses feel personal. ...

TL;DR for operators LLMs are not merely getting better at choosing the right emotion label. This paper shows that, inside their output distributions, larger models organise emotion words into increasingly rich hierarchies: broad emotions such as joy or sadness sit above more specific states such as optimism, disappointment, or grief.1 That matters because the hierarchy itself becomes an evaluation object. Instead of asking only whether a model correctly labels a customer message as “angry,” an operator can ask whether the model’s internal emotion map has enough depth, whether related emotions cluster sensibly, and whether that structure changes when the model is prompted to adopt different demographic personas. ...