> ## Documentation Index > Fetch the complete documentation index at: https://docs.amlok.io/llms.txt > Use this file to discover all available pages before exploring further. # Transaction language and annotation > A proposed bilingual labeling and adaptation protocol for financial descriptors and supporting documents. Financial descriptors compress names, rails, intermediaries, references, and purpose into incomplete strings. A language model can help interpret those strings, but it cannot recover information that the source never supplied. This page specifies the text-model study and annotation process. The [document and transaction benchmarks](https://docs.amlok.io/research/document-benchmarks.md) separate public-report extraction from private transaction interpretation; the current measured retrieval study does not validate transaction-language understanding. ## Separate the tasks | Task | Proposed output | Boundary | | - | - | - | | Descriptor parsing | Observed spans for rail, intermediary, name candidate, and reference | Preserve the original string and offsets. Do not manufacture a name. | | Purpose classification | Versioned category and confidence or abstention | A category is not proof of business purpose or tax treatment. | | Counterparty resolution | Candidate entity identifier linked to corroborating evidence | A plausible name match is not verified legal identity. | | Document extraction | Amount, currency, period, parties, and source location | Preserve ambiguous fields and extraction errors for review. | | Grounded explanation | A readable account of supplied evidence and calculations | No unsupported input, approval decision, or causal claim. | A descriptor containing an Interac marker can establish a possible payment rail while leaving the counterparty unresolved. A Stripe settlement identifies an intermediary; it does not identify each underlying buyer. Train and score those roles separately. ## Annotation unit and schema Use the descriptor plus the evidence that was available at the observation cutoff. Annotators must not see later outcomes or private information excluded from the model's task. Preserve an isolated-text task and a context-assisted task so added information is not mistaken for superior language understanding. | Annotation field | Meaning and admissible evidence | | - | - | | `source_record_id` | Stable identifier of the actual authorized source observation. | | `original_text` and `spans` | Unmodified descriptor and character offsets for observed information. | | `language` | Observed language or mixed/undetermined status. | | `rail` and `intermediary` | Payment rail and processor roles, separated from the underlying counterparty. | | `counterparty_candidate` | Proposed entity match, with candidate evidence and unresolved state. | | `purpose` | Versioned category, multiple plausible labels or unknown. | | `annotation_version` | Label-policy version, reviewer decisions and adjudication lineage. | | `evidence_ids` and `available_at` | Supporting records and their verified availability at the task cutoff. | This is a research annotation contract, not a new public API response. Populate it only from observed evidence. Label definitions specify inclusions, exclusions, ambiguity, multi-label cases and adjudication rules. Preserve negative and unresolved examples. ## Build an independent reference set Sample across institutions, formats, source families, English, French, code-switching, industries, and descriptor lengths. Retain natural prevalence for the main test and a separately reported challenge set for rare failures. Deduplicate templates and related entities before splitting. Otherwise, repeated merchant strings can make the task appear easier than identifying an unseen counterparty. Have two qualified annotators independently label a stratified sample. Record agreement by field and category, disagreements, adjudication, and the remaining unresolved share. Use bilingual annotators for French evidence. An agreement coefficient is informative only with its prevalence and label definitions; raw agreement alone can conceal poor performance on uncommon classes. Keep provider labels, rules, and teacher-model outputs as explicitly marked weak supervision. Estimate their error against adjudicated evidence. Do not use the same model's generated labels as the independent test of that model. Prevent final-test examples from entering prompt templates, few-shot exemplars, retrieval indexes, or annotation-training material. ## Proposed adaptation study Compare a transparent rule system, character-based retrieval, a compact multilingual encoder, an instruction model adapted for structured extraction, and hosted frontier models with matched evidence. Freeze each checkpoint revision and licence. Compare native French supervision with a translation pipeline; evaluate the final financial meaning rather than translation fluency alone. For a labeled sequence task, optimize the likelihood of the adjudicated structured target. For span tagging, use token-level supervision and evaluate complete spans as well as tokens. Optional continued language-model pretraining must use a separately approved corpus and be tested against a no-adaptation control. Prevent model-generated narratives from becoming financial labels without independent evidence. An initial parameter-efficient search can compare adapter ranks 8 and 16, learning rates 0.00005 and 0.0002, and one to three passes through the approved training set. These are **proposed search candidates**, not measured optimal settings or completed runs. Choose the model and sequence length from observed input lengths, available resources, and licence constraints. Reserve the final holdout before any search. ## Scoring and error analysis Report field-level exact match, span F1, category macro-F1, unresolved coverage, and false-resolution rate. Evaluate confidence on a separate calibration set. Measure precision at a required coverage and coverage at a required false-match tolerance. Do not count abstentions as correct resolved identities. Break errors down into missing source information, extraction failure, normalization error, wrong candidate retrieval, wrong entity merge, and unsupported inference. Report performance on unseen names and formats, language slices, and time-held-out evidence. Test malicious instructions embedded in descriptors and documents as untrusted content. Use the resulting evidence in the [entity graph](https://docs.amlok.io/research/entity-graph.md). A language prediction can propose an edge; corroboration, permissions, and temporal checks determine whether that edge is usable. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.