langchain/docs/extras/use_cases/more/graph
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
..
graph_arangodb_qa.ipynb docs: Update ArangoDB Links (#9251) 2023-08-15 07:43:47 -07:00
graph_cypher_qa.ipynb Add the option to use separate LLMs for GraphCypherQA chain (#9689) 2023-08-24 11:50:38 -07:00
graph_hugegraph_qa.ipynb Move graph use case to "more" section (#8997) 2023-08-14 17:20:38 -07:00
graph_kuzu_qa.ipynb Move graph use case to "more" section (#8997) 2023-08-14 17:20:38 -07:00
graph_memgraph_qa.ipynb docs: Add memgraph notebook (#9448) 2023-08-21 13:45:04 -07:00
graph_nebula_qa.ipynb Move graph use case to "more" section (#8997) 2023-08-14 17:20:38 -07:00
graph_qa.ipynb Move graph use case to "more" section (#8997) 2023-08-14 17:20:38 -07:00
graph_sparql_qa.ipynb Move graph use case to "more" section (#8997) 2023-08-14 17:20:38 -07:00
index.mdx Move graph use case to "more" section (#8997) 2023-08-14 17:20:38 -07:00
neptune_cypher_qa.ipynb Move graph use case to "more" section (#8997) 2023-08-14 17:20:38 -07:00
tot.ipynb Move graph use case to "more" section (#8997) 2023-08-14 17:20:38 -07:00