You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of #26, users can train generative models to normalize entity text after extraction: For example to standardize date or currency formats, or correct common OCR error patterns.
This is not ideal though, as the normalization model only sees the specific extracted text without the surrounding context (which could for example give locale cues whether a date is more likely to be MM/DD/YYYY or DD/MM/YYYY).
It would be better if we could directly merge a generative output onto the layout-aware model, and fine tune normalized extraction directly.
The text was updated successfully, but these errors were encountered:
As of #26, users can train generative models to normalize entity text after extraction: For example to standardize date or currency formats, or correct common OCR error patterns.
This is not ideal though, as the normalization model only sees the specific extracted text without the surrounding context (which could for example give locale cues whether a date is more likely to be MM/DD/YYYY or DD/MM/YYYY).
It would be better if we could directly merge a generative output onto the layout-aware model, and fine tune normalized extraction directly.
The text was updated successfully, but these errors were encountered: