Add LLM information extraction example#1595
Open
Sarthak-commits wants to merge 4 commits into
Open
Conversation
jernejfrank
reviewed
Jun 8, 2026
jernejfrank
left a comment
Contributor
There was a problem hiding this comment.
Hey, thankl you for submitting this. Could you also:
- save the dag representation as a PNG (driver has a method for this already) and embed it in the README?
- Create a jupyter notebook that does the same as
run.pyand allows users to walk through the example in that way (see other examples)?
Author
|
Yeah sure i will submit it, give me some time i am out of town for the moment. |
This file contains hidden or 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.
Closes #241.\n\nAdds a Hamilton LLM workflow example for structured information extraction from customer feedback. The example defines a Pydantic output schema, builds the extraction prompt, calls the OpenAI chat API, parses the JSON response, and validates it before returning serializable records.\n\nThe runner also supports a mocked response so the validation path can be exercised without an API key.