Skip to content
atlas
← Back to the entry

What it is

A large language model (LLM) is a deep learning model trained on very large amounts of text to do one thing: predict the next token (a word or part of a word) given the text so far. Repeating that single prediction thousands of times in a row produces paragraphs, summaries, translations, code and answers to questions. Chat assistants, writing aids in office suites and many “AI features” in business software are thin layers on top of an LLM.

The idea of statistical language models is old, but three developments made the current generation possible:

Today LLMs are offered as cloud services by large providers, as open-weight models that organisations can run themselves, and increasingly as components inside other products.

How it works

Training: learning how text usually continues

During pre-training the model reads enormous text collections - web pages, books, code, forums - and adjusts billions of internal weights so that its next-token guesses get better. Nothing in this process checks whether a statement is true; the model learns what text usually looks like. Afterwards, fine-tuning and feedback-based training shape its behaviour: answering politely, refusing clearly harmful requests, following a format.

Inference: one token at a time

When you send a prompt, the model breaks it into tokens, computes a probability for every possible next token, picks one, adds it to the text and repeats. The amount of text it can consider at once is its context window - from a few thousand to over a million tokens in current models. Anything outside the window, including earlier conversations, is simply not seen unless a system puts it back in.

Why it hallucinates

Because the model is optimised to produce plausible text rather than verified text, it sometimes produces fluent, confident statements that are false: invented sources, wrong figures, non-existent court cases. This is called hallucination, and it is a direct consequence of how the model is built, not a bug that will be patched away. Techniques such as retrieval-augmented generation (RAG) make it rarer and easier to spot, but do not remove it.

What it does not have

An LLM has no built-in database of facts, no awareness of today’s date unless told, and no separation between “instructions” and “data” - everything is text in the same window. That last point is the root of prompt injection.

What it means for an organisation and a coordinator

LLMs arrive in organisations from two directions: officially, through a licensed assistant or a feature in existing software, and unofficially, when staff paste work into a free chat service (shadow AI). The governance questions are largely the same:

A worked scenario

Freja is a GRC student on an internship at a Danish housing association. Staff have started using a chat assistant built on an LLM to draft emails to tenants and to sum up board meeting notes - exactly the situation described in the term’s short definition. Her manager asks her to draft a usage guideline.

She starts with a simple data classification: public information (published rules, general notices) may be used freely; internal information (meeting notes without personal data) only in the company’s licensed assistant, where the contract rules out training on customer data; confidential and personal data (tenant complaints, arrears, health information) not at all without a specific assessment. She checks that the provider has a data processing agreement and states where data is processed. She adds two rules for output: a person always reads and owns the final text, and figures or legal statements are checked against the source. Finally she records the assistant as an asset in the risk register, with hallucination and data leakage as named risks, and proposes a short awareness session so staff understand why the rules exist.

Common misunderstandings

Atlas is in beta.