SAG
SAG is a document search tool released by Zleap AI on July 14, 2026, which extracts complete events and the entities involved in each event from sentences, then constructs both relational and vector indexes. While conventional Retrieval-Augmented Generation (RAG) focuses on splitting documents into fixed-length chunks and retrieving semantically similar chunks, SAG adopts an approach that preserves event-level units corresponding to who did what, when, and how. When a query arrives, instead of traversing only a pre-fixed graph, it dynamically performs SQL joins
SAG is a document search tool released by Zleap AI on July 14, 2026. It extracts complete events and the entities involved within sentences, then constructs both relational and vector indexes. While conventional Retrieval-Augmented Generation (RAG) focuses on splitting documents into fixed-length chunks and finding semantically similar chunks, SAG adopts an approach that preserves event-level units corresponding to who did what, when, and how. Upon receiving a query, instead of traversing only pre-fixed graphs, SAG creates dynamic hyperedges using SQL joins and performs multi-hop searches connecting multiple events and entities. This is closer to assembling a temporary investigation board linking people, events, and documents tailored to the question, rather than merely finding pages with similar sentences in a library.
Existing Dense RAG excels at quickly retrieving documents with similar expressions but may miss intermediate relationships when questions require connecting facts scattered across multiple documents to form an answer. Conversely, GraphRAG approaches are strong in relationship exploration but incur costs for pre-defining and maintaining graph schemas and edges. The differentiator of SAG is that it does not simply merge the results of Dense RAG and GraphRAG; instead, it indexes event–entity structures and vector representations during the collection phase and dynamically generates relationships required by actual queries during the search phase. Consequently, even with the same document set, it can construct different connection paths depending on the query, aiming for a structure suitable for tracking event contexts or common participants rather than simple similar-phrase searches within single documents.
Life science researchers can build an event-centric search foundation in SAG by inputting materials where the same genes, drugs, and diseases appear repeatedly in different contexts, such as research papers, clinical trial public documents, and lab records. For example, by linking entities such as experiments inhibiting a specific target protein, observed phenotypes, and cell lines used, researchers can explore questions that require traversing multiple events, such as "When this target was inhibited, inflammatory markers decreased, but under what conditions were toxicities reported?" Search results can be passed to summarization models via REST or OpenAI-compatible APIs, or used as the evidence retrieval stage for research assistant agents through MCP integration. However, supported document formats, extraction models, chunking settings, reranking methods, and quantitative performance cannot be verified solely from the provided Discovery information, so official documentation verification is necessary before actual research application.
Another use case involves connecting reagents, batches, treatment conditions, and observation results in long-term accumulated experimental records into event–entity forms. Researchers can choose local desktop or Docker deployment and track conditions scattered across different lab notebooks based on SQL join paths generated at query time. In literature monitoring tasks, events extracted from new papers can be added to existing indexes, followed by multi-hop queries across drug–target–disease–adverse event relationships to narrow down candidates for subsequent review. However, local processing scope, external model invocation status, data retention policies, and API authentication methods are not included in the input information; therefore, deployment settings and security boundaries must be verified separately before injecting sensitive clinical or genomic data.
💻 System Requirements
Need to check whether a GPU is required and the officially recommended capacity.
Need to verify required capacity per application, model, and index.
⚡ Installation
4-1. Quick Start
Confirmation of the official installation command is required. While the Discovery information indicates support for local desktop and Docker deployments, it does not provide an install command that can be directly quoted.
4-2. Detailed installation
Verify the operating system-specific desktop installation procedures, Docker image names, required environment variables, model provider settings, data volumes, and port configurations from the GitHub README or official documentation before writing. Do not arbitrarily provide unverified commands.
🧬 Bio Use Cases
🔬 Literature-Based Drug–Target–Phenotype Tracing
Index drugs, target proteins, cell lines, and observed results from papers as event–entity pairs, then perform multi-hop queries using SQL joins. Supported file formats, extraction parameters, and search performance metrics must be confirmed via official documentation.
🧬 Condition–Result Link Search in Experimental Records
Extract reagents, batches, treatment conditions, and phenotypes from disparate experimental logs to construct relational and vector indexes. Pass search results to subsequent summarization steps via REST or OpenAI-compatible APIs, though exact API parameters and quantitative outcomes require verification.
📚 Research Trend Monitoring Agent Integration
Link events extracted from new literature to existing data and enable research assistant agents to query drug–disease–adverse event pathways via MCP. Update frequency, index scale, latency, and quality metrics require confirmation through official benchmarks.
FAQ
What is SAG?
SAG is a document search tool released by Zleap AI on July 14, 2026. It extracts complete events and the entities involved within sentences, then constructs both relational and vector indexes. While conventional Retrieval-Augmented Generation (RAG) focuses on splitting documents into fixed-length chunks and finding semantically similar chunks, SAG adopts an approach that preserves event-level units corresponding to who did what, when, and how. Upon receiving a query, instead of traversing only pre-fixed graphs, SAG creates dynamic hyperedges using SQL joins and performs multi-hop searches connecting multiple events and entities. This is closer to assembling a temporary investigation board linking people, events, and documents tailored to the question, rather than merely finding pages with similar sentences in a library. Existing Dense RAG excels at quickly retrieving documents with similar expressions but may miss intermediate relationships when questions require connecting facts scattered across multiple documents to form an answer. Conversely, GraphRAG approaches are strong in relationship exploration but incur costs for pre-defining and maintaining graph schemas and edges. The differentiator of SAG is that it does not simply merge the results of Dense RAG and GraphRAG; instead, it indexes event–entity structures and vector representations during the collection phase and dynamically generates relationships required by actual queries during the search phase. Consequently, even with the same document set, it can construct different connection paths depending on the query, aiming for a structure suitable for tracking event contexts or common participants rather than simple similar-phrase searches within single documents. Life science researchers can build an event-centric search foundation in SAG by inputting materials where the same genes, drugs, and diseases appear repeatedly in different contexts, such as research papers, clinical trial public documents, and lab records. For example, by linking entities such as experiments inhibiting a specific target protein, observed phenotypes, and cell lines used, researchers can explore questions that require traversing multiple events, such as "When this target was inhibited, inflammatory markers decreased, but under what conditions were toxicities reported?" Search results can be passed to summarization models via REST or OpenAI-compatible APIs, or used as the evidence retrieval stage for research assistant agents through MCP integration. However, supported document formats, extraction models, chunking settings, reranking methods, and quantitative performance cannot be verified solely from the provided Discovery information, so official documentation verification is necessary before actual research application. Another use case involves connecting reagents, batches, treatment conditions, and observation results in long-term accumulated experimental records into event–entity forms. Researchers can choose local desktop or Docker deployment and track conditions scattered across different lab notebooks based on SQL join paths generated at query time. In literature monitoring tasks, events extracted from new papers can be added to existing indexes, followed by multi-hop queries across drug–target–disease–adverse event relationships to narrow down candidates for subsequent review. However, local processing scope, external model invocation status, data retention policies, and API authentication methods are not included in the input information; therefore, deployment settings and security boundaries must be verified separately before injecting sensitive clinical or genomic data.
When should I use SAG?
SAG is a document search tool released by Zleap AI on July 14, 2026, which extracts complete events and the entities involved in each event from sentences, then constructs both relational and vector indexes. While conventional Retrieval-Augmented Generation (RAG) focuses on splitting documents into fixed-length chunks and retrieving semantically similar chunks, SAG adopts an approach that preserves event-level units corresponding to who did what, when, and how. When a query arrives, instead of traversing only a pre-fixed graph, it dynamically performs SQL joins
What is a biomedical use case for SAG?
🔬 Literature-Based Drug–Target–Phenotype Tracing: Index drugs, target proteins, cell lines, and observed results from papers as event–entity pairs, then perform multi-hop queries using SQL joins. Supported file formats, extraction parameters, and search performance metrics must be confirmed via official documentation.
📝 Update Notes
- vfnos-v1.5.11-fnos10/1/2026
SAG 도구가 1.5.11 버전으로 업데이트되었습니다. 이번 릴리즈는 새로운 FPK 파일을 포함하고 있어, 기존 분석 환경의 최신화와 시스템 안정성 확보를 위해 확인이 필요해요. 구체적인 기능 변화는 명시되지 않았지만, 연구 데이터 처리의 일관성을 유지하기 위해 최신 패키지 적용 여부를 검토해 보세요.
- vv1.8.109/22/2026
이번 SAG v1.8.10 업데이트에서는 업데이트 프로세스가 사용자 선택형으로 변경되어, 연구 작업 중 의도치 않은 프로그램 종료나 자동 설치를 방지할 수 있습니다. 특히 Windows 환경에서 기존 지식베이스나 재구성 기록이 사용자 확인 없이 삭제되지 않도록 개선되어, 소중한 실험 데이터와 기록을 더욱 안전하게 보호할 수 있습니다. 다만, 업데이트 방식이 변경됨에 따라 구버전 사용자는 안정적인 전환을 위해 안내된 브릿지 버전을 먼저 거쳐야 하니 참고해 주세요.
- vv1.8.79/13/2026
SAG v1.8.7 업데이트에서는 엑셀(XLS/XLSX) 데이터 임포트 시 표 구조가 유지되지 않던 문제가 해결되어, 실험 데이터나 제품 정보가 서로 뒤섞이는 오류를 방지할 수 있어요. 또한 엔진의 오류 처리 로직이 개선되어 복구 불가능한 오류가 반복되는 현상을 막고 시스템의 안정성을 높였답니다. 데이터의 정확성과 무결성이 중요한 생명공학 연구원분들에게 이번 업데이트는 더욱 신뢰할 수 있는 분석 환경을 제공할 거예요.
🧪 Related Code of Life
No related Code of Life posts yet.