Description
Preserve a historical term-use date transcription and explicit precision.
Critical annotations distinguish source voices, editorial insertions, omission markers, edition locators and caller-assigned interpretations. Case preservation and half-open text offsets describe representation rather than meaning. A bracketed token or source-role label does not verify faithful quotation, authority, an argument or its historical context.
Preserve a historical term-use date transcription and explicit precision.
When to use this tool
Use Historical Label Use Date Precision when you already have labelText, dateText, suppliedPrecision and need to preserve a historical term-use date transcription and explicit precision.
How to use the tool and how it works
- Enter labelText, dateText, suppliedPrecision. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read token. Use the output convention below.
Enter labelText, dateText, suppliedPrecision 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 field | Meaning and units | Accepted input |
|---|---|---|
| labelText | Label Text | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| dateText | Date Text | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| suppliedPrecision | Supplied Precision | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"labelText": "Term A",
"dateText": "circa 1900",
"suppliedPrecision": "approximate year"
},
"output": {
"token": "[\"Term A\",\"circa 1900\",\"approximate year\"]"
}
}Limitations and assumptions
- The result records supplied values without validating a historical claim. 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
Read the original passage and relevant edition with the stated interpretive and editorial conventions. Verify source context and attribution before reuse; local span labels and interpretation-objection pair keys organize records without evaluating the argument or granting quotation rights.
References
Similar or alternative tools
- Editorial Normalization Disclosure Tag
Record an explicit editorial normalization disclosure.
- Discourse Role Caller Code Pair
Record an ordered pair of explicitly supplied discourse-role codes.