Exploring Claude/GPT Knowledge Cutoffs and Pre-Training Timelines
1–10 of 21 posts
Re: Exploring Claude/GPT Knowledge Cutoffs and Pre-Training Timelines
#2This was great! One thing that wasn't addressed that I always assume, is that a marketing name like "Opus 5" is not a single model, but many models, versions and gets minor updates over time.
I also assumed many questions get routed to simpler models or programs to answer correctly, but it almost surprisingly didn't seem that way from the post.
Anyways, great post.
Re: Exploring Claude/GPT Knowledge Cutoffs and Pre-Training Timelines
#3So Jan 2026 latest, I guess we are due to 2 OOM’s better retraining over the coming years. Curious to see the point at which AI plateaus.
Re: Exploring Claude/GPT Knowledge Cutoffs and Pre-Training Timelines
#4Great read and interesting analysis! I’m less charitable toward Anthropic supposedly not distilling ChatGPT for training purposes. Maybe not today, but during the GPT-4 era when Anthropic was the underdog - I can see it happen. Packaged along with some of Amodei’s clever jumping through hoops to prove how that is, in fact, virtuous.
Re: Exploring Claude/GPT Knowledge Cutoffs and Pre-Training Timelines
#5I wonder if this kind of analysis will give us a way to check if the frontier labs are waiting for the right moment to release their models.
To me it feels obvious that these companies are not releasing models as soon as they are done doing their post training / testing with any new model.
But there is no real way to know how much of this "waiting" any lab is doing, if we can get better estimates this way maybe we can gauge how far the open weights models really are.
Re: Exploring Claude/GPT Knowledge Cutoffs and Pre-Training Timelines
#6I wonder if this kind of analysis will give us a way to check if the frontier labs are waiting for the right moment to release their models. To me it feels obvious that these companies are not releasing models as soon as they are done doing their post training / testing with any new model. But there is no real way to know how much of this "waiting" any lab is doing, if we can get better estimates this way maybe we ca…
It’s also worth to say that developers in general always have one more thing to fix before a release but if their hand is forced they can push it straight into main!
Re: Exploring Claude/GPT Knowledge Cutoffs and Pre-Training Timelines
#7I wonder if this kind of analysis will give us a way to check if the frontier labs are waiting for the right moment to release their models. To me it feels obvious that these companies are not releasing models as soon as they are done doing their post training / testing with any new model. But there is no real way to know how much of this "waiting" any lab is doing, if we can get better estimates this way maybe we ca…
Given how competitive the space is any form of waiting seems like it has more downside than upside to me.
If you have the new "best" model you may only have a few weeks of time in the market before some other lab releases a new model that beats yours.
This means you should get it out ASAP so you can maximize the time during which your model is "best". Once your model isn't best any more you're going to lose a lot of revenue to the new leader.
Re: Exploring Claude/GPT Knowledge Cutoffs and Pre-Training Timelines
#8great read
Re: Exploring Claude/GPT Knowledge Cutoffs and Pre-Training Timelines
#9From my own experiments with various models, I suspect that LLMs have distinct/partitioned cutoff dates; for example, historical literature doesn't change (Greek history, Shakespeare, Goethe), general knowledge (updated only in certain areas), technologies (updated regularly), software also remains surprisingly stable - for example, with GIT, a basic command set is sufficient to do 99% of the jobs - new features are unknown or unnecessary, and tabloid knowledge, which is always up-to-date (politics, Taylor Swift albums).
Re: Exploring Claude/GPT Knowledge Cutoffs and Pre-Training Timelines
#10From my own experiments with various models, I suspect that LLMs have distinct/partitioned cutoff dates; for example, historical literature doesn't change (Greek history, Shakespeare, Goethe), general knowledge (updated only in certain areas), technologies (updated regularly), software also remains surprisingly stable - for example, with GIT, a basic command set is sufficient to do 99% of the jobs - new features are…
I would have thought that as well but at least for coding vs world event facts I didn't see obvious differences in cutoffs