NE

Google's Sample Usage prints NE(2,3) with no result; TRUE is DERIVED from the page's one-line definition and its "Equivalent to the `<>` operator" clause. Google's NE page, read live on 2026-08-31 at https://support.google.com/docs/answer/3093981. BATCH PROVENANCE (batch H, the first Sheets/LibreOffice-only batch). Every function in this batch has x == false in docs/data/compat.json: it is a Google Sheets function that Microsoft does not document at all, so this corpus makes NO claim about it in that engine and nothing here is measured against that vendor's documentation. The authority is Google's own support.google.com function page, cited by full URL and by the date it was read -- Google publishes no version number for these pages, so a bare URL dates nothing. WHAT GOOGLE ACTUALLY PRINTS, WHICH IS LESS THAN IT LOOKS: most of these pages carry a 'Sample Usage' block of FORMULAS WITH NO RESULTS. Where a value below is Google's own published output the note says so; where it is derived from the page's stated semantics the note says that instead, and says from which sentence. No value in this batch was taken from a search snippet, a blog or a mirror. LIBREOFFICE: probed on all four pinned builds (24.2.0.3, 24.8.7.2, 25.2.0.3, 25.8.7.3) in five storage spellings -- plain, _xlfn., COM.MICROSOFT., ORG.OPENOFFICE. and _xlfn.ORG.OPENOFFICE. -- and #NAME? under every one of them, so the expected values below describe Google Sheets and the LibreOffice column records absence. THE PAGE SAYS NOTHING ABOUT TEXT. None of the six comparison-operator pages (EQ, NE, GT, GTE, LT, LTE) makes any statement about comparing text to text, text to numbers, mixed types, or case sensitivity, and none of them prints a single result value; their Examples sections are embedded live spreadsheets whose cells are not part of the article text. So this file asserts text behaviour only STRUCTURALLY -- the function must agree with the operator it is documented to be equivalent to, whatever that operator does -- and never asserts what the comparison itself yields on text.

The same comparison through cell references. The page names A2 and A3 without populating them, so this corpus chose 2 and 3 to match the literal sample. Google's NE page, read live on 2026-08-31 at https://support.google.com/docs/answer/3093981.

Derived from the exact wording of the definition and the `<>` equivalence. This is the case that separates NE from its neighbours, and Google publishes no example of it. Google's NE page, read live on 2026-08-31 at https://support.google.com/docs/answer/3093981.

A STRUCTURAL assertion with no derived constant, and deliberately so: the page never says how text compares, or whether the comparison is case sensitive, so the only thing it licenses is that the function and the operator must return the SAME answer. This case asserts that agreement and nothing about the answer itself. Google's NE page, read live on 2026-08-31 at https://support.google.com/docs/answer/3093981.

Google's Sample Usage prints NE(2,3) with no result; TRUE is DERIVED from the page's one-line definition and its "Equivalent to the `<>` operator" clause. Google's NE page, read live on 2026-08-31 at https://support.google.com/docs/answer/3093981. BATCH PROVENANCE (batch H, the first Sheets/LibreOffice-only batch). Every function in this batch has x == false in docs/data/compat.json: it is a Google Sheets function that Microsoft does not document at all, so this corpus makes NO claim about it in that engine and nothing here is measured against that vendor's documentation. The authority is Google's own support.google.com function page, cited by full URL and by the date it was read -- Google publishes no version number for these pages, so a bare URL dates nothing. WHAT GOOGLE ACTUALLY PRINTS, WHICH IS LESS THAN IT LOOKS: most of these pages carry a 'Sample Usage' block of FORMULAS WITH NO RESULTS. Where a value below is Google's own published output the note says so; where it is derived from the page's stated semantics the note says that instead, and says from which sentence. No value in this batch was taken from a search snippet, a blog or a mirror. LIBREOFFICE: probed on all four pinned builds (24.2.0.3, 24.8.7.2, 25.2.0.3, 25.8.7.3) in five storage spellings -- plain, _xlfn., COM.MICROSOFT., ORG.OPENOFFICE. and _xlfn.ORG.OPENOFFICE. -- and #NAME? under every one of them, so the expected values below describe Google Sheets and the LibreOffice column records absence. THE PAGE SAYS NOTHING ABOUT TEXT. None of the six comparison-operator pages (EQ, NE, GT, GTE, LT, LTE) makes any statement about comparing text to text, text to numbers, mixed types, or case sensitivity, and none of them prints a single result value; their Examples sections are embedded live spreadsheets whose cells are not part of the article text. So this file asserts text behaviour only STRUCTURALLY -- the function must agree with the operator it is documented to be equivalent to, whatever that operator does -- and never asserts what the comparison itself yields on text.

The same comparison through cell references. The page names A2 and A3 without populating them, so this corpus chose 2 and 3 to match the literal sample. Google's NE page, read live on 2026-08-31 at https://support.google.com/docs/answer/3093981.

Derived from the exact wording of the definition and the `<>` equivalence. This is the case that separates NE from its neighbours, and Google publishes no example of it. Google's NE page, read live on 2026-08-31 at https://support.google.com/docs/answer/3093981.

A STRUCTURAL assertion with no derived constant, and deliberately so: the page never says how text compares, or whether the comparison is case sensitive, so the only thing it licenses is that the function and the operator must return the SAME answer. This case asserts that agreement and nothing about the answer itself. Google's NE page, read live on 2026-08-31 at https://support.google.com/docs/answer/3093981.

Google's Sample Usage prints NE(2,3) with no result; TRUE is DERIVED from the page's one-line definition and its "Equivalent to the `<>` operator" clause. Google's NE page, read live on 2026-08-31 at https://support.google.com/docs/answer/3093981. BATCH PROVENANCE (batch H, the first Sheets/LibreOffice-only batch). Every function in this batch has x == false in docs/data/compat.json: it is a Google Sheets function that Microsoft does not document at all, so this corpus makes NO claim about it in that engine and nothing here is measured against that vendor's documentation. The authority is Google's own support.google.com function page, cited by full URL and by the date it was read -- Google publishes no version number for these pages, so a bare URL dates nothing. WHAT GOOGLE ACTUALLY PRINTS, WHICH IS LESS THAN IT LOOKS: most of these pages carry a 'Sample Usage' block of FORMULAS WITH NO RESULTS. Where a value below is Google's own published output the note says so; where it is derived from the page's stated semantics the note says that instead, and says from which sentence. No value in this batch was taken from a search snippet, a blog or a mirror. LIBREOFFICE: probed on all four pinned builds (24.2.0.3, 24.8.7.2, 25.2.0.3, 25.8.7.3) in five storage spellings -- plain, _xlfn., COM.MICROSOFT., ORG.OPENOFFICE. and _xlfn.ORG.OPENOFFICE. -- and #NAME? under every one of them, so the expected values below describe Google Sheets and the LibreOffice column records absence. THE PAGE SAYS NOTHING ABOUT TEXT. None of the six comparison-operator pages (EQ, NE, GT, GTE, LT, LTE) makes any statement about comparing text to text, text to numbers, mixed types, or case sensitivity, and none of them prints a single result value; their Examples sections are embedded live spreadsheets whose cells are not part of the article text. So this file asserts text behaviour only STRUCTURALLY -- the function must agree with the operator it is documented to be equivalent to, whatever that operator does -- and never asserts what the comparison itself yields on text.

The same comparison through cell references. The page names A2 and A3 without populating them, so this corpus chose 2 and 3 to match the literal sample. Google's NE page, read live on 2026-08-31 at https://support.google.com/docs/answer/3093981.

Derived from the exact wording of the definition and the `<>` equivalence. This is the case that separates NE from its neighbours, and Google publishes no example of it. Google's NE page, read live on 2026-08-31 at https://support.google.com/docs/answer/3093981.

A STRUCTURAL assertion with no derived constant, and deliberately so: the page never says how text compares, or whether the comparison is case sensitive, so the only thing it licenses is that the function and the operator must return the SAME answer. This case asserts that agreement and nothing about the answer itself. Google's NE page, read live on 2026-08-31 at https://support.google.com/docs/answer/3093981.