Probate Parsing Solution #8
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1. OCR using pytesseract - ocr.py 2. Named Entity Recognition using NLTK and Stanford NLP Wrapper a)NLTK - nltk_ner.py b)Stanford NLP - stanford_ner.py 3. To get a good idea of prerequisites and execution details - README.md
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Refer Issue #7
The system that I propose to implement is an end-to-end system that extracts the text from probate books and seeds them into a database with entities such as name, county, date, relationships etc. This system can, therefore, be broken down into three phases -
Due to lack of samples to train a Named Entity Recognizer, I've made use of the Stanford NER Wrapper and NLTK to produce the results.