SQL-RAG · EVENT-ENTITY RETRIEVAL
SAG
Searchable. Connected. Traceable.
Turn scattered documents into structured knowledge and source-grounded Agent answers. SAG is a local-first, open-source knowledge base built around an original retrieval architecture instead of stitching traditional RAG and GraphRAG together.
Product overview
Two perspectives. One traceable knowledge base.


Why SAG
Keep complete semantics in Events. Build relationships at query time.
SAG neither maintains two retrieval systems nor precomputes global hyperedges. For the current question, SQL connects events through shared entities to create a focused local candidate space.A verifiable knowledge path
Ingest once. Preserve evidence through retrieval and reuse.
Import
Normalize files and web pages to Markdown
Index
Build Chunk, Event, and Entity representations
Retrieve
Use semantic recall and query-time hyperedges
Trace
Return every result to its source evidence
Reuse
Connect Agents, APIs, MCP, and Python
System boundary
One engine. Three entry points.
Use the complete workspace, build a custom interface on the self-hosted API, or embed zleap-sag directly in a Python service. Every path shares the same knowledge engine.Complete product
Search, converse, and explore the same knowledge.
Inspect retrieval before an Agent uses it, and open the source behind every result.
Select knowledge scope, observe tool activity, and keep important claims attached to clickable citations.
Discover relationships across events, entities, and timelines, then return from any node to source evidence.
Public benchmarks
Best in 8 of 9 Recall@1/2/5 metrics.
With the same BGE-Large-EN-v1.5 Embedding and Qwen3.6-Flash LLM configuration, SAG reports average Recall@2 of 79.30% and Recall@5 of 88.18% across three multi-hop QA datasets.Read the paper and full resultsStart with SAG