\n ## System Architecture Diagram: Two-Phase Knowledge Graph Processing for Question Answering ### Overview The image is a technical system architecture diagram illustrating a two-phase process for building and utilizing a knowledge graph to answer queries. The system is divided into an **offline "Graph Construction"** phase and an **online "Retrieve and Answer"** phase, separated by a vertical dashed line. The diagram uses icons, text labels, and flow arrows to depict data flow and processing steps, with a focus on integrating causal reasoning via Large Language Models (LLMs). ### Components/Axes The diagram is segmented into two primary regions: **1. Left Region: Graph Construction (Offline)** * **Header Label:** "Graph Construction (Offline)" * **Process Flow (Top Path):** * Icon: Document stack. Label: "Raw Texts" * Arrow with icon (magnifying glass) and label: "IE" (Information Extraction) * Icon: Network graph. Label: "Knowledge Graph" * Arrow with icon (cube) and label: "Embed" * Icon: Database/server rack. Label: "Vector Store" * **Process Flow (Bottom Path):** * Arrow from "Raw Texts" with icon (split arrow) and label: "Partition" * Label: "Hierarchical Graph" * Arrow with icon (link) and label: "Identify Causality" * Text below arrow: "LLM" * Arrow points to label: "Graph with Causal Gates" * **Visual Elements:** * Two sets of stacked, layered graph illustrations. * Left set: Labeled "Hierarchical Graph". Shows three layers of graphs (top, middle, bottom) with nodes and edges. No special highlighting. * Right set: Labeled "Graph with Causal Gates". Shows three corresponding layers. Specific edges and nodes are highlighted in **blue**, indicating the "causal gates" identified by the LLM. * Layer labels on the right side: "Hn" (top), "Hn-1" (middle), "H0" (bottom). **2. Right Region: Retrieve and Answer (Online)** * **Header Label:** "Retrieve and Answer (Online)" * **Process Flow:** * Icon: Person/User. Label: "Query" * Arrow with icon (magnifying glass) and label: "Embed and Score" * Icon: Checkmark in circle. Label: "Top K entities" * Arrow with label: "N hop via gates, cross modules" * Label: "Context Subgraph" * Arrow with icon (link) and label: "Distinguish Causal vs Spurious" * Text below arrow: "LLM" * Arrow points to label: "Context" * Final arrow with label: "with Query" pointing to icon (checkmark) and label: "Answer" * **Visual Elements:** * Two sets of stacked, layered graph illustrations, mirroring the offline phase. * Left set: Labeled "Context Subgraph". Shows a subset of the hierarchical graph. Some nodes/edges are highlighted in **blue**, representing the retrieved subgraph. * Right set: Labeled "Context". Shows the same subgraph structure, but now a specific path or set of elements is marked with a **blue checkmark**, indicating the causal context selected for the answer. ### Detailed Analysis The diagram details a pipeline that transforms raw text into a structured, causally-aware knowledge representation for efficient question answering. **Offline Phase (Graph Construction):** 1. **Dual-Path Processing:** Raw texts are processed in two parallel streams. * **Stream 1 (Direct KG):** Texts undergo Information Extraction (IE) to build a standard Knowledge Graph, which is then embedded into a Vector Store for similarity search. * **Stream 2 (Hierarchical & Causal):** Texts are partitioned and organized into a Hierarchical Graph (layers Hn to H0). An LLM analyzes this graph to "Identify Causality," resulting in a "Graph with Causal Gates." The blue highlights in the right-hand graph illustration show these gates—specific connections deemed causally significant. 2. **Output:** The outputs are a Vector Store (for retrieval) and a Causal Graph (for reasoning). **Online Phase (Retrieve and Answer):** 1. **Query Processing:** A user query is embedded and scored against the Vector Store to retrieve the "Top K entities." 2. **Subgraph Retrieval:** Starting from these entities, the system traverses "N hops" through the graph, guided by the "gates" (causal connections) established offline, to assemble a "Context Subgraph." 3. **Causal Filtering:** An LLM processes this subgraph to "Distinguish Causal vs Spurious" relationships, filtering it down to the most relevant "Context." 4. **Answer Generation:** The final causal context, combined with the original query, is used to generate the "Answer." ### Key Observations * **Central Role of LLMs:** LLMs are explicitly called out for two critical reasoning tasks: identifying causal relationships in the offline phase and distinguishing causal from spurious links in the online phase. * **Hierarchical Structure:** The use of a hierarchical graph (Hn...H0) suggests the knowledge is organized at multiple levels of abstraction or granularity. * **Causal Gates as a Core Mechanism:** The "causal gates" (highlighted in blue) are the key innovation. They act as filters or guides during the online retrieval ("N hop via gates") to focus the search on causally relevant paths, improving efficiency and answer quality. * **Visual Consistency:** The blue highlighting is used consistently across both phases to denote causally significant elements, creating a clear visual link between the offline analysis and online application. ### Interpretation This diagram presents a sophisticated architecture for **causality-aware knowledge graph question answering**. The core problem it solves is the retrieval of not just any relevant information, but *causally pertinent* information from a large knowledge base. * **How it Works:** The system pre-computes causal relationships (offline) to create a "map" of meaningful connections. When a query arrives (online), it doesn't just search broadly; it follows this pre-defined causal map to quickly home in on the context that likely contains the answer, ignoring spurious correlations. * **Why it Matters:** This approach addresses key limitations of standard retrieval-augmented generation (RAG). By focusing on causal links, it aims to: 1. **Improve Accuracy:** Retrieve more relevant context, reducing hallucinations. 2. **Increase Efficiency:** Limit the search space via gates, reducing computational cost. 3. **Enhance Explainability:** The causal path from query to answer is more traceable. * **Underlying Assumption:** The architecture assumes that causality is a powerful heuristic for relevance in question answering. The LLM's role is to encode this causal understanding into the graph structure itself, which then guides the retrieval process deterministically. The separation into offline and online phases is a practical design to handle the computational cost of causal analysis.