Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update README.md #271

Merged
merged 1 commit into from
Mar 14, 2024
Merged

Update README.md #271

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,22 @@ See [documentation](https://eyurtsev.github.io/kor/).

Integrated with the [LangChain framework 😽💗 🦜🔗](https://python.langchain.com/en/latest/index.html).

## Kor vs. LangChain

There are 3 different approaches for extracting information using LLMs:

1. [prompt based/parsing](https://python.langchain.com/docs/use_cases/extraction/how_to/parse)
2. [function/tool calling](https://python.langchain.com/docs/use_cases/extraction/quickstart)
3. JSON mode

Please see the LangChain [extraction use case docs](https://python.langchain.com/docs/use_cases/extraction/) for an overview.

Kor has a pretty good implementation of the **parsing** approach. The approach works with all good-enough LLMs regardless
of whether they support function/tool calling or JSON modes.

Extraction quality is principally driven by providing good reference examples and good schema documentation.

Please see guidelines [here](https://python.langchain.com/docs/use_cases/extraction/guidelines) and [here](https://eyurtsev.github.io/kor/guidelines.html).

## Version 1.0.0 Release

Expand Down
Loading