[GH-ISSUE #3412] Add knowledge cutoffs for different available models #2103

Open
opened 2026-04-12 12:20:41 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @hamirmahal on GitHub (Mar 30, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/3412

What are you trying to do?

No response

How should we solve this?

I think it'd be nice if the table at https://github.com/ollama/ollama?tab=readme-ov-file#model-library had a Knowledge Cutoff column with the month and year of a model's knowledge cutoff.

What is the impact of not solving this?

Different users have to manually look up the knowledge cutoff of different models themselves.

Anything else?

No response

Originally created by @hamirmahal on GitHub (Mar 30, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/3412 ### What are you trying to do? _No response_ ### How should we solve this? I think it'd be nice if the table at https://github.com/ollama/ollama?tab=readme-ov-file#model-library had a `Knowledge Cutoff` column with the month and year of a model's knowledge cutoff. ### What is the impact of not solving this? Different users have to manually look up the knowledge cutoff of different models themselves. ### Anything else? _No response_
Author
Owner

@JamesClarke7283 commented on GitHub (Apr 6, 2024):

I think this would be nice to have,
You could make it inherit the knowledge cutoff from the model it was based upon specified in the FROM instruction, if they don't specify one in the Modelfile.

<!-- gh-comment-id:2041040162 --> @JamesClarke7283 commented on GitHub (Apr 6, 2024): I think this would be nice to have, You could make it inherit the knowledge cutoff from the model it was based upon specified in the `FROM` instruction, if they don't specify one in the `Modelfile`.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#2103