> There are a few reasons why people may argue about the answer to a mathematical question like “8 / 2(2+2)”. One reason is that there is more than one wav to interpret the question and arrive at a different answer. For example, some people may interpret the question as “8 / (2 * (2+2))” and arrive at an answer of 1, while others mav interpret it as “(8 / 2) * (2+2)” and arrive at an answer of 16.
Wow, this is kinda astonishing. Could it ruminate about the precedence of the operators?
Also: the words "may" and "way" appear as "mav" and "wav" in your text. Is this a problem with your input to the HN comment or did the model really make these textual errors?
Replace "2+2" with "2-2" and the answer is still the same. It does not read expressions, it does not see divisions by zero. It just outputs the training data, associated with parenthesis.
It will still hallucinate "division by zero" fallacies when asked questions like:
Given that a - b > 0, can we simplify?
a / (a - b) = 1 / (a - b)
a = 1
Regarding the issue of "mav", it looks like the poster used screen capture followed by some image-to-text OCR routine (possibly tesseract). This feels like an OCR fail.
Exactly what happened. I was capturing some of my earlier conversations as screenshots, and didn't feel like retyping the whole thing. Errors are mine, apologies.
Wow, this is kinda astonishing. Could it ruminate about the precedence of the operators?
Also: the words "may" and "way" appear as "mav" and "wav" in your text. Is this a problem with your input to the HN comment or did the model really make these textual errors?