THub Technical Documentation
  • Introduction
  • 🔗 LangChain
    • 🕵️ Agents
    • 🗄️Cache
    • ⛓️Chains
    • 🗨️Chat Models
    • 📁Document Loaders
    • 🧬Embeddings
    • Graph
    • 🧠Large Language Models(LLM)
    • 💾Memory
    • 🛡️Moderation
    • 👥Multi Agents
    • 🔀Output Parsers
    • 📝Prompts
    • 📊Record Managers
    • 📑Retrieval-Augmented Generation
    • 🔍Retrivers
    • Sequential Agent
    • ✂️Text Splitters
    • 🛠️Tools
    • 🔌Tools (MCP)
    • 🗃️Vector Stores
  • 🦙LLama Index
    • 🕵️ Agents
    • 🗨️Chat Models
    • 🧬Embeddings
    • 🚀Engine's
    • 🧪Response Synthesizer
    • 🛠️Tools
    • 🗃️Vector Stores
Powered by GitBook
On this page
  1. 🔗 LangChain

Graph

A Graph is a canvas where you can assemble various nodes to define the flow of data and operations. Each node represents a distinct operation, such as data input, processing,decision-making,or output.

Previous🧬EmbeddingsNext🧠Large Language Models(LLM)

Last updated 2 days ago

1)Neo4j

The Neo4j node allows THub to interact with Neo4j, a leading graph database that stores data as nodes and relationships. This integration is particularly beneficial for applications requiring understanding of complex relationships, such as recommendation systems, fraud detection, and semantic search.


Key Features

  • Graph-Based Retrieval: Utilizes Cypher queries to fetch data based on intricate relationships, enabling more nuanced data retrieval compared to traditional databases.

  • Vector Search Capabilities: Neo4j can function as a vector store, allowing similarity searches alongside traditional graph queries.

  • Integration with LangChain: Aligns with LangChain's support for Neo4j, facilitating seamless incorporation into existing AI pipelines.

  • Support for Retrieval-Augmented Generation (RAG): Combines graph data retrieval with language models to generate contextually rich responses.


Configuration Requirements

To set up the Neo4j node in THub, you'll need:

  • Neo4j Connection Details: Database URI, username, and password.

  • Cypher Queries: Custom queries to retrieve the desired data from your graph database.

  • Optional: Vector index configurations if leveraging vector search capabilities.


GitHub
GitHub
GitHub