Understand text
Intents, sentiment, topics.
A language model estimates the probability of sequences of words or tokens in a language. Trained on large corpora, it predicts the next element and can complete, classify, or generate text. Modern architectures often use transformers (Vaswani et al., 2017). It is not a guaranteed knowledge base—it is a statistical model of language.
In one sentence
A language model predicts the most likely continuation of text.
Key points
Term at a glance
Historically n-grams and RNNs; today attention and transformers dominate. “Attention Is All You Need” paved the way for massive models.
An LM can be trained for a task (sentiment) or self-supervised then adapted. Size and data drive capability and cost.
For an SME, “using a language model” often means calling an API or open-weights model—with a business layer (prompts, RAG, validation) around it.
Classification, extraction, generation, summary—clear metric.
Small local model vs LLM API by sensitivity and volume.
RAG, JSON schemas, refusal lists.
Business test sets, human review, drift monitoring.
A Montreal accounting firm uses a model to classify client emails (urgent / invoice / general) before routing. The model never decides a tax amount—a human validates. Precision on 500 historical messages sets the automation threshold.
Intents, sentiment, topics.
Emails, summaries, rewrites.
Structured fields from documents.
With embeddings derived from the model.
| Language model | Large language model (LLM) | |
|---|---|---|
| Scale | Can be small / specialized | Very large, general-purpose |
| Few-shot ability | Variable / limited | Often strong without fine-tuning |
| Cost | Often lower | Higher (API or GPUs) |
| Control | Sometimes easier to bound | Powerful but harder to master |
They speed text processing (support, documents, marketing) when framed well. ROI comes from minutes saved and errors avoided—not the generative demo.
It models statistical patterns; human-like “understanding” is a useful but misleading metaphor.
Rarely at first. Prompting, RAG, or light fine-tuning often suffice.
No. For business facts, use verifiable sources (RAG, APIs).
Test on local phrasings; add glossary and examples in the prompt or RAG base.
Want to automate text without losing business control? We pick model scale and guardrails that fit.
Frame your LM use