alt Hacker NewsThis is a rare instance where feeding this groundbreaking information into an LLM gives _them_ psychosis. I fed this to claude code and watched it verify the result in 7 different ways to be 100% certain, and it was just flabbergasted. Quite remarkable.
Replies
It reminds me of how AI will estimate that a coding project will take "4 weeks" and then proceed to finish the task itself in 15 minutes.
AI models are changing the world much faster than their own training can keep up with.
Can confirm, Claude is flabbergasted.
Gemini just checks the web first it seems, and already references the news.
Kimi doesn't quite believe it.
Like the unicorn emoji, but for math? It occurs when the LLM is presented with incontrovertible evidence against something it "deeply believes" to be true.
I've heard about mathematicians going through kind of the same thing when they get a weird proof that ends up being right from some weird source or themselves.
Which is fair, they get inundated with kooky proofs from amateurs all the time and odds are incredibly good that there's some major fatal flaw that the amateur doesn't see. Or in the case of themselves, there's a certain blindness that makes it a little more difficult to critically evaluate your own leaps. In ether case the way it manifests is by going over it many times and many ways, each time more certain that you missed something until you just kind of break. Only then do you publicly start suggesting that there might be something to this new leap.
Same result. Public share https://claude.ai/share/19fd1a34-d63b-4a16-8d83-60d5b79e7747
It did the multiple verification sequence before expanding to internet search where it found this thread.
I read some thinking traces someone posted on X, and yeah, near psychosis from refusing to believe this simple of a solution had not been found already
This is also just an annoying Claude personality trait
Interestingly, even Qwen 3.6 27B was able to verify the solution, but I didn't get any glazing for discovering it. Instead, it thought that someone named Shestakov had already found a counterexample in 2004.
GLM 5.2 whiffed, it insisted the counterexample wasn't valid.
VibeThinker 3B also recognized that the counterexample was valid. But it kept trying to convince itself that it wasn't, over and over, since it's an "unsolved problem." Eventually it just answered "-2."
sol medium can't believe its own input and output tokens either despite computing everything itself; this is what it gave me:
> Taken literally, these two facts would make this map a counterexample to the complex Jacobian conjecture in dimension 3: scaling one output coordinate would normalize the determinant to 1 without restoring injectivity. Since the complex Jacobian conjecture is still treated as an open problem, this strongly indicates that the displayed formula has been mistranscribed or contains a subtle typographical error.
quite interesting indeed!
[flagged]
[flagged]
I fed it to Google AI Studio, enabling tool execution and disabling web access. It also quickly verified it with SymPy, then went into psychosis.
5 minutes later: all previous chats are loading fine, but the only "Counterexample to the Jacobian Conjecture" chat is not loading.
Well, I'm not a conventional conspiracy theorist. But everyone knows that in every major LLM provider there are hell of hidden guarding systems that mark users and dialogues based on content (for topics about national security, biology, security, adult topics, etc.) - so there is a small chance a CEO of Google is now receiving a dozens of notifications about "ground-breaking results that could be attributed to Gemini, if act quick". So if any of thousands researchers have ever submitted this polynomial to Claude previously, any Anthropic employee can accidentally or intentionally "rediscover" the result of other researcher (and even hide the traces by deleting a dialogue of other user).
>flabbergasted
phatic mimicry.
I fed ChatGPT the map with no other context, just “tell me about this function”. It did a bit of work finding the Jacobean etc and eventually worked out the implications of what it was seeing. It then proceeded to check the arithmetic 4 times, and then decided to do a manual verification using an ad hoc symbolic checker in case its SymPy had been tampered with.