← Back to Dictionary

Were

Podcast 1 · Introduction

Were /wɜː/ · verb (past tense of "be")

A short documentary narration — meaning, origin, and how the word is used.

In this introduction, Were means a past tense form of the verb be, which is why the course on be belongs with it. Cambridge defines were, and the American entry records were. Background sits in the article on copula.

Ready
Podcast 2 · Daily Use

In Conversation

Two British speakers using "were" naturally in everyday talk.

Ready
Podcast 3 · Prompt Engineering

Prompting with "were"

An instructor and developer explore real, copy-ready AI prompts built around the word.

Ready
1 / 3

Transcript: “Were” vocabulary micro-course

Read along with the three podcasts, or open the full dictionary entry for Were for the definition, Arabic meaning, synonyms and example sentences.

Podcast 1 — Introduction & meaning

Narrator: Today's word is were — a verb, pronounced WUR, IPA /wɜː/.

Narrator: Were is a past tense form of the verb be — used with you, we, and they, and also in special if-clauses about things that aren't true.

Narrator: Plain English: we say I was, but you were, we were, they were. Were is the plural and you past of be.

Narrator: It comes from the Old English wǣron, an ancient form of be, part of one of the oldest verbs in the language.

Narrator: Be is wildly irregular, built from several old roots — am, is, are, was, were — and were covers a key part of its past.

Narrator: There's a special use too: the subjunctive. We say if I were you, not if I was you, when talking about something imaginary or wished-for.

Narrator: That subjunctive were is the mark of careful English — if she were here, as if it were true, I wish it were so.

Narrator: The register is completely neutral and everyday, though the subjunctive were carries a slightly more polished, formal air.

Narrator: Were is the past of being, shared among many — and the gentle word we reach for when we dream of what is not.

Read podcasts 2 and 3

Podcast 2 — In conversation

Speaker A: We were just talking about you! We were wondering where you were all morning.

Speaker B: I was stuck in traffic. You were lucky you weren't with me — it was chaos. Were the others on time, at least?

Speaker A: They were, yes. So it was just you. There's one thing I always second-guess, though — is it if I was you or if I were you?

Speaker B: Ah, the classic. It's if I were you — always were there. That's the subjunctive, for things that aren't real. You're not me, so it's were.

Speaker A: So with imaginary or wished-for things, I use were even with I?

Speaker B: Exactly. I wish I were taller. If it were possible. As if she were here. Were for the dream; was for plain past fact.

Speaker A: And normally it's I was but you were, we were, they were?

Speaker B: Right. Was goes with I, he, she, it. Were goes with you, we, they — and with anything imaginary.

Speaker A: So the common mistake is if I was you.

Speaker B: That's the one. Polished English says if I were you. Spelled W-E-R-E — simple, but it does a lot of work.

Podcast 3 — Prompt engineering

Speaker B: Let's look at how were works in AI prompts. As a past and conditional word it's perfect for history views and what-if scenarios.

Speaker A: Were for past states and what-ifs — the AI shows how things were or could be?

Speaker B: Exactly. It frames the past and the hypothetical. First prompt — a history view:

Prompt: Build a dashboard showing what the numbers were last month. Display where sales were, where costs were, and how things were compared to now, so the team sees how things were before.

Speaker B: Were tells the AI you want the past state — a clear before-picture to compare against today.

Speaker A: The history view is clear. What about a what-if tool?

Speaker B: Here, using the conditional:

Prompt: Build a what-if calculator. Let users ask what their savings would be if interest were higher, show the result as if the rate were doubled, and compare it with how things are now.

Speaker A: A what-if were tool — practical. For a database?

Speaker B: Try this:

Prompt: Design a snapshots table that records what values were. Store what each setting was at a point in time, index the date, and let me query what the values were on any past day.

Speaker A: Past values cleanly stored — tidy. For an audit view?

Speaker B: Like this:

Prompt: Build an audit screen showing who the editors were. List who the owners were before each change, what the fields were, and how things were, so we can trace what they were previously.

Speaker A: Showing who the editors were — useful. And a simulation?

Speaker B: Here:

Prompt: Build a budget simulator using if it were. Let users explore what the total would be if costs were lower, show each result as if the change were real, and reset to how things are.

Speaker A: An if-it-were simulator — clever.

Speaker B: One small word for the past and the hypothetical. Use were in a prompt and the AI builds clear history views and what-if tools around it.