AI glossary
A token is the unit text is counted in, the context window is how much text the model sees at once, and a parameter has nothing to do with either. This glossary defines forty nine common terms in four branches: models, training, working with a model, and safety and error.
- Lesson 15 of 15
- Beginner
- Free, no signup
The four branches these terms fall into
-
twelve terms
Models and how they are built
What a model is made of, what it is measured by and how it runs.
-
twelve terms
Training and data
Work done before the model reached you, and already finished.
-
thirteen terms
Working with a model
The everyday working terms, and the ones most often confused.
-
twelve terms
Safety, error and rights
The terms that start to matter once the work gets serious.
The order of the branches is a learning order, not an order of importance. If you are just starting, the third branch is useful to you before the first two.
Last checked: Facts and tool names in this lesson are re-checked against their sources on this date.
Models and how they are built
These twelve terms are about the model itself: what it is made of, what it is measured by and how it runs.
Large language model: a program trained on a large volume of text whose job is to predict the most likely continuation of a text. Everything you do with it, from translation to writing code, is a form of that one job.
Parameter: a number inside the model that is set during training and determines part of the final behaviour. The parameter count tells you the size of the model, not its quality.
Weights: the trained parameters themselves, as a file you can download and run. Open weights means that file has been published, not that the training code and data have been.
Transformer: the neural network architecture most of today models are built on. Its defining feature is the attention mechanism, which lets the model look at the rest of the text while processing each piece of it.
Token: a piece of text the model counts in, usually smaller than a word. Costs and limits are all measured in tokens rather than words.
Context window: the largest number of tokens a model can see at once, covering both your input and the answer it produces. When a conversation grows long its beginning falls out of the window and the model no longer has it.
Multimodal model: a model that understands more than one kind of input, such as text, images and audio. Being multimodal does not mean being good at all of them.
Reasoning model: a model that produces more intermediate steps before answering, in order to break a problem down. Its answer comes back slower and costs more, and it is not worth it for a simple question.
Open weight model: a model whose weight file has been published so you can run it on your own hardware. Open is a matter of degree and each model licence has to be read separately.
Model card: the document a maker publishes alongside a model, stating its capabilities, limits and terms of use. It is the first thing to read before building on a model.
Quantisation: shrinking a model by reducing the numeric precision of its weights so it fits on weaker hardware. In exchange for less memory, output quality drops a little.
Inference: the stage of using a trained model to get an answer, entirely separate from training. The cost of every request you send belongs to this stage.

Training and data
These twelve terms are about work that was done before the model reached you and finished once and for all.
Training: the process in which a model parameters are set by exposure to a large volume of data. It is expensive, takes months, and once it is over it does not continue through your conversation.
Training data: the collection of text, images and audio a model was trained on. Any bias or error present in that collection finds its way into the behaviour of the model.
Pretraining: the first and largest stage of training, where the model learns general patterns of language from raw data. What comes out of this stage is not an assistant yet, only a text predictor.
Fine tuning: retraining a finished model on smaller, more specialised data so its behaviour moves closer to one task. It is not a substitute for a good prompt and only makes sense when you have many consistent examples.
Reinforcement learning from human feedback (RLHF): a stage in which people rank the model answers and the model learns which shape of answer is preferred. This is the stage that turns a text predictor into something resembling an assistant.
Distillation: building a smaller model by training it on the output of a larger one. The result is cheaper and faster and usually does not reach the same quality on hard work.
Knowledge cutoff: the date up to which the training data of a model was collected. Anything that happened after it is not in the model, however confidently it talks about it.
Overfitting: when a model memorises the training data instead of learning the pattern and performs poorly on new data. In evaluations it shows up as a suspiciously high score.
Bias: a systematic tilt of the model toward one answer or one group, coming from the training data or from the training process itself. Bias differs from random error because it repeats in one direction.
Benchmark: a standard test for comparing models on a defined task. A high benchmark score does not guarantee the model is better at your real work, because the test conditions are not your conditions.
Data labelling: the human work of marking what each data sample is or which answer is better. A large part of model quality rests on this rarely seen work.
Synthetic data: data that is itself the output of one model and is used to train another. It is cheap, and used carelessly it carries the errors of the first model into the second.
Working with a model
The thirteen terms that come up most in daily work, and the ones most often confused.
Prompt: the text you give a model so it can produce an answer. Everything written in the conversation is part of the prompt, not only the last message.
System prompt: the fixed instruction a maker or developer gives the model before your conversation, setting its general behaviour. You usually do not see it, yet it affects every answer you get.
Prompt engineering: the work of writing and revising a prompt until the output comes close to what you want. Most of it is clear writing and very little of it is tricks.
Few shot: putting a few example inputs and outputs inside the prompt so the model picks up the format you want. It is the best route for work that is hard to describe but easy to demonstrate.
Chain of thought: asking the model for intermediate steps before the final answer. It improves results on multi step problems and only makes a simple question longer.
Temperature: the setting that governs how far the model reaches toward less likely options. A low number gives more uniform, more predictable output; a high one gives more variety and less stability.
API: the route by which your program talks to the model directly, with no graphical interface. Data policy and pricing on that route usually differ from the consumer plan.
Conversation memory: what a tool keeps from your earlier conversations and places in front of the model again. It is not the same as the context window: the window is a limit on one request, memory is a product feature.
Retrieval augmented generation (RAG): a method where relevant pieces of your documents are found and added to the prompt before the model answers. It is the usual way to make a model answer from your own data without training it.
Embedding: turning a text into a list of numbers that represents its meaning, so that texts close in meaning can be found. Semantic search and the retrieval stage above both run on this.
Structured output: forcing the model to answer in a defined format such as JSON so a program can consume it directly. Without it the output is prose and differs slightly every time.
Tool calling: the capability that lets a model request a function or a search instead of answering, and then use the result. It is the foundation of what gets called an agent.
Agent: a system that puts a model in a loop so it can work with tools and carry several steps in sequence. What separates it from a chatbot is that it does not only answer, it does something.
The four pairs that get confused most
-
Parameter or token
A parameter sits inside the model and stays fixed after training. A token is a piece of text that passes through the model each time.
-
Training or inference
Training happened once, before release. Inference repeats every time you send a message.
-
Context window or memory
The context window is a limit on one request and belongs to the model. Memory is a product feature that puts old text back into the prompt.
-
Chatbot or agent
A chatbot answers and stops there. An agent calls tools and carries several steps in sequence.
All eight terms are defined separately higher up this page. These cells add no new definition, they only show the boundary.
Safety, error and rights
The twelve terms that start to matter once the work gets serious, and that are usually missing from marketing copy.
Hallucination: when a model produces something that looks right but is not real, such as a source that does not exist or a number that appears nowhere. It comes from the prediction mechanism rather than from a fault, so the next version does not remove it entirely.
Prompt injection: when text the model reads, such as a web page or an email, contains an instruction aimed at the model, and the model carries it out. For agents with access to the internet or to files this is the central risk.
Jailbreak: an attempt to get around a model behavioural rules through the way a request is phrased. Makers keep closing them and new ones keep appearing.
Watermark: a mark embedded into the output at the moment of generation so it can later be identified as machine made. It only works on the output of models that embed it, and it is read with that maker own tool.
Content provenance (C2PA): a standard for recording the creation and editing history of a file inside the file. It differs from a watermark: this is metadata that can be stripped, while the other is a mark inside the content itself.
Deepfake: an image, video or voice generated by AI to resemble a real person. The problem it raises is not technical, it is consent and deception.
Alignment: the work of making a model behave in accordance with human intent and values. It is an open research problem, not a feature that gets ticked off one day.
Guardrail: a restriction placed outside the model itself to block a particular output or behaviour. Because it sits outside the model it is both configurable and bypassable.
AI detector: a tool that guesses whether a text was written by a machine. Its output is a probability rather than a verdict, and it errs more on non English text and on edited text.
Training opt out: a setting or a right that stops your data being used to train the next model. It does not stop storage or human review, which are two separate things.
Copyright of output: the question of who owns the text or image a model produced and whether it is protected at all. The answer depends on the country and on the terms of the service, and it is changing; we issue no general ruling here.
Sycophancy: a model tendency to agree with the user rather than disagree correctly. It is why asking what do you think of my idea gets a low value answer, and asking what would break this idea gets a better one.
Words whose meaning changes in marketing
The five words below have clear meanings in technical writing and almost none in marketing copy. Telling the difference is the skill a glossary should hand you.
Smart. On its own it says nothing. The right question is which decision this system makes and on what input; if there is no clear answer, ignore the adjective.
It learns. A deployed model usually does not learn from your usage. That is what the split between training and inference means, and what products call learning is almost always conversation memory, that is keeping text and putting it back into the prompt. If it really is being trained, the place for that claim is the product data policy, not its sales page.
No hallucinations. This claim does not fit the mechanism. The chance of error can be lowered by retrieving from a source and by checking the output, but no is a promise that no serious maker writes in its documentation.
Open source. This one is a spectrum. The Open Source Initiative has published its own formal definition of open source AI, and many models called open do not meet it, because only the weights were released and the licence carries commercial restrictions. Read each model licence separately before you build a product on it.
Free. A free plan is a point in a data policy, not only a price. It is the place where the chance of your input being used to improve the product is at its highest, and we set out the detail with a per vendor table in the privacy in AI tools lesson.
The practical test for any AI claim is the ordinary one: if this sentence were false, what would be different? A claim with no way of being false is not a claim, it is decoration.
Which claim has a way of being false
Checkable
- This model score on a named benchmark, with a link to that table
- The name of the model licence, with a link to the licence text
- Business plan data is not used for training, with a link to the data policy
- The knowledge cutoff of this model is a stated date, per the model card
Not checkable
- The smartest model in the world
- No hallucinations and one hundred percent accurate
- It learns from you, without saying where that is documented
- Fully open source, without naming the licence
The second list is not necessarily false. It simply has no way of being false, and that is what turns a claim into an advertisement.
The fast path, with AI
A glossary nobody maintains goes stale, and new terms usually appear first on an English page rather than in a Persian glossary. The fast path is this: instead of asking the model for a definition, ask it to pull the definition out of that page and quote the sentence verbatim. The output then becomes checkable, and checking it is one command.
- Save the whole page you want to understand: a model card, vendor documentation, or an article. Keep the text in a file, because step three needs it.
- Feed the text with the prompt below. The task asked for is extraction rather than generation, so a fast cheap model handles it.
- Search each quoted sentence in the original file. A row whose sentence is not found gets deleted, because it did not come from the text.
- The rows that survive are your personal glossary of that page. The rows marked the text does not define this are the ones to look up elsewhere, and that short list is the one worth spending time on.
Copy-ready recipe
The text below is a technical page.
{paste the text or the model card here}
Give me the list of specialist terms in this text. For each term, exactly three columns:
term | plain language equivalent | a sentence quoted verbatim from this text containing it
Rules:
- Only terms that appear literally in the text above. Add no term from your own knowledge.
- The third column must be word for word from the text: not a summary, not a paraphrase.
- If the text does not itself define a term, write "the text does not define this"
in the third column and do not bring a definition from anywhere else.
# then check every quoted sentence against the original file:
grep -F -c "the exact quoted sentence" source.txt
Before you trust the output: The whole value of this method is in that last command. If you do not check the quoted sentences you have moved trust from one place to another and nothing more. Two things that happen in practice: the model sometimes changes one word of a sentence, at which point it keeps its meaning but is no longer a quotation, and the eye misses that while grep does not. Second, this method pulls a definition out of a text rather than out of reality: if the page itself is wrong then the output is wrong, and checking the quote does not reveal it.
AI in this kind of work
To learn vocabulary, the best move is to tie the model to a text rather than to its memory. Paste a technical page and ask it to pull the terms out of that text and quote their sentences. Our position is blunt: never ask a model what a term means and believe the answer as it stands. If the term was coined after the model knowledge cutoff, the answer is fabricated in the same confident tone and you have no way to tell.
Tools that actually help
- Claude It suits pulling terms out of a long text, and when you say plainly to quote only from the text it adds less of its own. Iran is not on Anthropic supported countries list; we read that on their own page.
- NotebookLM It is built for exactly this: you upload the document and its answers are tied to that document. When you are putting several model cards and documentation pages side by side, it beats pasting by hand.
- Gemini It handles Persian well and is a comfortable choice for finding a Persian equivalent of a new term. Always weigh its suggested equivalent against an existing Persian text, because coining equivalents is exactly the work that gets done confidently and without a source.
Where it backfires
Two terms from this list lead straight to a wrong decision when they are half understood. First watermark: Google DeepMind own page says SynthID embeds digital watermarks directly into AI generated images, audio, text or video, that the watermarks are embedded across Google generative AI consumer products, and that they are imperceptible to humans but can be detected by SynthID technology. That single sentence carries two conditions that usually get dropped: only the output of models that embed it, and read with that maker own tool. AI is detectable is not a general property. Second open source: the Open Source Initiative has published its own formal definition of open source AI, and many models called open do not meet it because only the weights were released and the licence is restricted. If you are building a product on a model, read its licence rather than its press description.
Sources: Google DeepMind: SynthID Open Source Initiative: the Open Source AI Definition
Where this advice stops
A glossary is a photograph of today. Some of these terms are barely two years old and some will have fallen out of use by next year; the check date at the top of the page is the only thing to lean on. Two more boundaries. The definitions here are practical rather than academic: a researcher would define several of them, alignment and agent in particular, differently, and that disagreement is real rather than a matter of taste. And this page is not the place for numbers: context window sizes, prices and model rankings live in the data files of the AI section of this site, because those change every month and the definition of a word does not.
From our own work
One rule was followed in writing this page, and you can check it yourself: not one of these forty nine definitions names a specific model or a version number. Search the four definition sections and you will not find one. The reason comes from running the AI section of this same site: there we keep data files where every number carries the date it was recorded, and where a table cell is left empty when the maker published no number, rather than filled with an estimate. Keeping the two apart, definitions on one page and numbers elsewhere with a date, is the only thing that saves a reference page from going stale in three months.
Real follow-up questions
What is the difference between AI, machine learning and deep learning?
They are nested rather than parallel. AI is the largest circle, machine learning is a subset of it and refers to methods that learn behaviour from data, and deep learning is a subset of machine learning that uses multi layer neural networks. The language models you work with today sit inside all three circles. The what is AI lesson shows the nesting as a figure.
Why is the parameter count not a good measure?
Because it states size, not quality. A smaller model trained on better data with a better method beats a larger one on real work, and that has kept happening for several years now. More parameters usually means more cost to run and more latency, and both of those are costs to you.
If I only have time for four terms, which ones?
Token, context window, prompt and hallucination. With those four you can see why costs are counted the way they are, why the model forgets the beginning of a long conversation, why answers change when you rewrite one sentence, and why a number it gives you cannot be trusted. The rest become necessary once the work gets more serious.