10,976 karma · joined April 24, 2021
This is one of the only benchmarks that actually matters for testing the frontier however. Other benchmarks can be gamed by simply being more persistent, but HLE is a diverse set of open-ended research-level questions. It tests domain knowledge and problem solving skills. Burning more reasoning tokens may help somewhat but not as much as e.g. coding benchmarks.
You only have weights (large immutable memory), or context (small mutable memory).
Humans have mutable long-term memory: I can learn a new skill, adapt an old skill to new information, or learn new knowledge today that I couldn't perform/didn't know yesterday. I don't have a training cutoff.
Context engineering is an attempt to paper over this limitation. You can get really far with context engineering and huge models, but you will never get to AGI because there are many tasks where humans' mutable long-term memory outperforms.
For example, a human can invent a new musical instrument and then learn how to play the instrument they just invented. That's inference (inventing an instrument) leading to training (neuroplasticity). Humans have the ability to train our NNs with considerably fewer training samples. Everything that you can do with transformers is in one causal direction: training -> inference.
Yes if you're doing backend the pelicans are probably completely irrelevant but if developing anything with a UI, you probably want a model that understands the relationship between code and what the user is seeing.
I can't wait for the future where I need a burner phone and a robotic arm just to browse the internet.
It would be better to compare models at how well they can write the code for chess engines, otherwise it's just saying that Fable is not a good CPU emulator, which is obvious.
The 3.5-4o era models were trained by RLHF primarily to write in a way that's pleasing to humans.
Starting with o1 the focus switched to reasoning, coding and benchmarks. If you remember when GPT-5 came out it introduced a new "colder" writing style (which was partly intentional) which made a certain subsection of Reddit Very Upset that Sam Altman had killed their AI boyfriends and they forced him to reinstate the warmer 4o.
The artificial default voice of modern models is optimized for reasoning efficiency rather than understandability. Unfortunately the artificialness has a tendency to leak out into the output tokens because reasoning tokens and output tokens are all still just tokens. You can prompt recent models to write in a more understandable style and they do a fairly good job of it, but it's not the default anymore, which means you will have to keep re-prompting it.
I don't think it's an unfixable problem, Anthropic in particular are just not very motivated to fix it because Claude is much less popular for chat than ChatGPT is.
There's nothing wrong with the English per se, it's grammatically correct, it just sounds so "Claude". Claude talks using pithy word soups that lack the niceties and structure of human writing.
If you're going to serve us slop then at least serve us good slop, give it a pass through GPT 5.6 to clean up the English.
If they ask after you've eaten, that would be rude, from my British perspective.
I believe they have made display answer a tool call so that it can keep updating its answer as it thinks, instead of doing all the reasoning up front, essentially inverting the usual flow. You can use this pattern with any model that supports tool calling.
The primary resource you need to train LLMs is money and China has plenty of that.
1) an extremely high financial incentive to be dishonest (trillions of dollars),
2) low-ish chance of being caught, especially if you launder the data through another model to remove identifying information,
3) the people in charge of said operations are generally agreed to be snakes,
then it should at least arouse suspicion. You may be right that get enough data from opt-ins that they don't need to do it. I do believe that they don't violate enterprise ZDR agreements, but for normal subscriptions I'm much less confident.
What's much more likely is that your US AI provider is promising not to train on your data but is doing so anyway. With a self-hosted model you can at least avoid that.
Providers will generally keep your session in cache for at least 5 minutes, possibly hours. The exact cache policy depends on the provider.
If your session expires from cache then the next time you send a message you will have to pay for all the tokens you had used in context up until that point again. e.g. if you have 200k tokens in context then if your session goes cold and you send a message after expiry you will have to pay for those 200k tokens again.
With 1M contexts especially you have to be extremely careful that you don't end up resubmitting requests for hundreds of thousands of tokens again and again.
Try to get yourself and the model to use disk for medium-term context rather than model context, that way it's much easier to /clear and restart if you need to go to the bathroom or something.