Skip to content

Main content

Claim Negation Marker Count Tool

Count literal supplied negation markers without determining scope or truth of a claim.

Loading tool…

Description

Locate literal negation-marker tokens under a case policy.

Scholarly annotation can preserve term senses, agent roles and source frames using explicit labels. Literal agreement, a recognized marker or an unambiguous record key organizes those assertions without establishing their meaning, truth or scholarly authority.

Locate literal negation-marker tokens under a case policy.

When to use this tool

Use Claim Negation Marker Count when checking one explicit annotation, marker or source-identity convention.

How to use the tool and how it works

  1. Enter tokens, suppliedMarkers, caseSensitive. Keep parallel arrays aligned. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read count, positions. Use the output convention below.

Locate literal negation-marker tokens under a case policy. Optionally lowercase tokens and suppliedMarkers, deduplicate the marker vocabulary and return matching zero-based positions and count.1

Input fieldMeaning and unitsAccepted input
tokensTokensRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
suppliedMarkersSupplied MarkersRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
caseSensitiveCase SensitiveRequired. Boolean.
Output fieldInterpretationReturned shape
countCountRequired. Safe integer.
positionsPositionsRequired. Array of safe integer; maximum items 256.
json
{
  "input": {
    "tokens": [
      "NOT",
      "a",
      "never"
    ],
    "suppliedMarkers": [
      "not",
      "never"
    ],
    "caseSensitive": false
  },
  "output": {
    "count": 2,
    "positions": [
      0,
      2
    ]
  }
}

Limitations and assumptions

  • Tokenization and marker vocabulary are supplied; matches do not determine linguistic negation scope or claim truth.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Inspect the source text and interpretive framework for substantive analysis; use source-aware annotation and bibliographic tools for complete records.

References

  1. Calculation and input contract: critical-theory/claim-negation-marker-count — tool.io

Similar or alternative tools