Create phenopackets from clinical case reports (WIP) #13
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
justaddcoffee
changed the title
|
Closing this PR I just wanted to know how well a naive case report -> LLM -> phenopacket workflow works, and I think the answer is "not very well". Most ontology terms are not actually correct (i.e. the concept is not in the paper) and often the ID and labels do not match |
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.
An experimental PR to make phenopackets directly from papers using LLMs
Also added code to generate phenopackets from papers mentioned in HPOA, so we can see how well this works, per convo with @julesjacobsen @caufieldjh and other hackathon people