> For the complete documentation index, see [llms.txt](https://sp.jerrygems.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sp.jerrygems.tech/volume-iv-the-indicative-engine-and-verb-conjugation/28-verbs-that-change-meaning-in-the-past.md).

# 28. Verbs That Shift Meaning in the Past

> *How saber, conocer, querer, and poder switch definitions between Preterite and Imperfect.*

***

## Verbs with Shifting Identities

Because the Preterite focuses on a sudden beginning or final outcome, while the Imperfect focuses on an ongoing state, these verbs completely shift their English translation:

| Verb          | In the Imperfect (Ongoing State / Background)   | In the Preterite (Punctual Inception or Outcome)  |
| ------------- | ----------------------------------------------- | ------------------------------------------------- |
| **Saber**     | *Sabía* = I already knew the fact               | *Supe* = I found out / discovered right then!     |
| **Conocer**   | *Conocía* = I was already familiar with him     | *Conocí* = I met him for the very first time      |
| **Querer**    | *Quería* = I wanted to / felt like it           | *Quise* = I actively attempted to do it           |
| **No querer** | *No quería* = I didn't feel like it             | *No quise* = I refused point-blank!               |
| **Poder**     | *Podía* = I had the general capacity/permission | *Pude* = I succeeded / managed to pull it off!    |
| **Tener**     | *Tenía una carta* = I possessed a letter        | *Tuve una carta* = I received a letter right then |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://sp.jerrygems.tech/volume-iv-the-indicative-engine-and-verb-conjugation/28-verbs-that-change-meaning-in-the-past.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
