Skip to content

Main content

Premise Relevance Source Annotation

Preserve an explicit premise-relevance annotation and source without determining relevance.

Loading tool…

Description

Preserve an explicit premise-relevance annotation and source.

Formal annotations separate declared truth values, domain assumptions, variable lists and source interpretations. A direct self-reference differs from an indirect cycle, and one self-loop differs from a globally reflexive relation. Local token operations do not parse a complete argument, derive its assumptions or establish truth or validity.

Preserve an explicit premise-relevance annotation and source.

When to use this tool

Use Premise Relevance Source Annotation when you already have premiseId, suppliedRelevanceWording, annotationSource and need to preserve an explicit premise-relevance annotation and source.

How to use the tool and how it works

  1. Enter premiseId, suppliedRelevanceWording, annotationSource. 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 token. Use the output convention below.

Enter premiseId, suppliedRelevanceWording, annotationSource using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1

Input fieldMeaning and unitsAccepted input
premiseIdPremise IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
suppliedRelevanceWordingSupplied Relevance WordingRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
annotationSourceAnnotation SourceRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
tokenTokenRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "premiseId": "P17",
    "suppliedRelevanceWording": "relevant to claim A",
    "annotationSource": "Rater A"
  },
  "output": {
    "token": "[\"P17\",\"relevant to claim A\",\"Rater A\"]"
  }
}

Limitations and assumptions

  • The result records supplied values without determining relevance. Sources and asserted relationships are not independently authenticated.
  • 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

Parse or formalize the complete expression and declared semantics when validity is the question. Inspect the full reference or accessibility relation for cycles and global properties; a supplied annotation, self-loop or variable list establishes only its local predicate.

References

  1. Calculation and input contract: philosophy/premise-relevance-source-annotation — tool.io

Similar or alternative tools