Description
Preserve an explicit gloss abbreviation, supplied expansion and source.
Language-processing records distinguish tokens, code points, UTF-16 positions and UTF-8 byte offsets. Tag grammars and local transition checks do not validate a full annotation sequence. Log-loss units determine perplexity conversion, while identifier suffixes may be textual labels rather than ordinary decimal numbers.
Preserve an explicit gloss abbreviation, supplied expansion and source.
When to use this tool
Use Morphological Gloss Abbreviation Source Row when you already have glossToken, suppliedExpansion, sourceId and need to preserve an explicit gloss abbreviation, supplied expansion and source.
How to use the tool and how it works
- Enter glossToken, suppliedExpansion, sourceId. 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 glossToken, suppliedExpansion, sourceId 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 |
|---|---|---|
| glossToken | Gloss Token | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| suppliedExpansion | Supplied Expansion | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| sourceId | Source Id | 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": {
"glossToken": "PST",
"suppliedExpansion": "past",
"sourceId": "G4"
},
"output": {
"token": "[\"PST\",\"past\",\"G4\"]"
}
}Limitations and assumptions
- The result records supplied values without inventing a universal gloss vocabulary. 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
Validate the complete corpus format, tokenizer, annotation sequence and scoring convention. Use a full parser or model evaluation when needed, preserving the exact offset unit, vocabulary and log base rather than inferring them from a local transformation.
References
Similar or alternative tools
- Phoneme Feature Single Contrast
Compare two supplied values of a named phonological feature.
- Morpheme Boundary Byte Offset
Count UTF-8 bytes preceding a supplied morpheme boundary.