langchain/docs/api_reference
Tomaz Bratanic dacf96895a
Add the option to use separate LLMs for GraphCypherQA chain (#9689)
The Graph Chains are different in the way that it uses two LLMChains
instead of one like the retrievalQA chains. Therefore, sometimes you
want to use different LLM to generate the database query and to generate
the final answer.

This feature would make it more convenient to use different LLMs in the
same chain.

I have also renamed the Graph DB QA Chain to Neo4j DB QA Chain in the
documentation only as it is used only for Neo4j. The naming was
ambigious as it was the first graphQA chain added and wasn't sure how do
you want to spin it.
2023-08-24 11:50:38 -07:00
..
_static/css Page per class-style api reference (#6560) 2023-06-30 09:23:32 -07:00
templates Update api references (#8646) 2023-08-04 16:10:58 -04:00
themes rm sklearn links (#8773) 2023-08-04 14:28:00 -07:00
conf.py docs:misc fixes (#9671) 2023-08-23 22:36:54 -07:00
create_api_rst.py Fix API reference docs (#9321) 2023-08-16 15:56:54 -07:00
guide_imports.json Add the option to use separate LLMs for GraphCypherQA chain (#9689) 2023-08-24 11:50:38 -07:00
index.rst Page per class-style api reference (#6560) 2023-06-30 09:23:32 -07:00
make.bat Doc refactor (#6300) 2023-06-16 11:52:56 -07:00
Makefile Doc refactor (#6300) 2023-06-16 11:52:56 -07:00
requirements.txt pin pydantic api ref build (#9556) 2023-08-21 12:11:49 -07:00