New data extraction models #3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
@eliribble @ned
Per the discussion in #1, here are the two foundational documents for the modality-based knowledge graph refactor:
field-reference.md— Complete field spec for all 5 workflow domains (Feature Observation, Inspection, Treatment, Access Assessment, Safety Assessment). Each field lists its trigger word, description, and enum values pulled from the ontology. 24 fields total. Pure field reference for implementation.utterances.yaml— 20 technician utterances mapped to structured fields, based on real field transcriptions fromnote-audio.csv:structurednaturalfeature:,inspection:,treatment:), no property-level trigger words.Each utterance maps all 27 fields — absent values are excluded from the output.
How this connects to the modality proposal in #1:
The field reference defines what each mode needs to extract. The utterances provide training data for each mode's parser — structured colon-delimited pairs for the feature/treatment modes and natural conversational speech for the fallback.
Files attached:
20260722-field-reference.md20260722-utterances-review.mdHey @ned, is this useful? Are there any gaps?