Implement input API and processor for EVEX database #1393
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
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.
This PR implements an API and processor for the EVEX text mining database (http://evexdb.org/). The approach is to use the "network" relations file as the backbone of INDRA Statement extraction. However, to gather evidence text, raw agent text and coordinates, and other metadata, it is necessary to find support for each relation in raw standoff output files. This latter part is considerably complicated since network relations aren't explicitly linked to elements of the standoff output. The processor produces around 620k Statements (each with a single Evidence), and more than 99% of these contain evidence text meaning these were successfully identifier from standoff files.