semantic search
technique judged 99% likely a named technique or architecture
See how it has spread across media tiers
Mentions over time
Table view
| Week | Articles | Sources |
|---|---|---|
| 2022-W04 | 1 | 1 |
| 2022-W25 | 1 | 1 |
| 2022-W28 | 1 | 1 |
| 2023-W51 | 1 | 1 |
| 2024-W02 | 1 | 1 |
| 2024-W11 | 1 | 1 |
| 2024-W13 | 1 | 1 |
| 2024-W15 | 1 | 1 |
| 2024-W19 | 1 | 1 |
| 2024-W22 | 1 | 1 |
| 2024-W23 | 1 | 1 |
| 2024-W24 | 1 | 1 |
| 2024-W25 | 2 | 2 |
| 2024-W26 | 1 | 1 |
| 2024-W29 | 1 | 1 |
| 2024-W34 | 1 | 1 |
| 2024-W52 | 1 | 1 |
| 2025-W01 | 1 | 1 |
| 2025-W11 | 1 | 1 |
| 2025-W19 | 1 | 1 |
| 2025-W23 | 2 | 1 |
| 2025-W47 | 1 | 1 |
| 2026-W04 | 1 | 1 |
| 2026-W07 | 3 | 1 |
| 2026-W09 | 2 | 1 |
| 2026-W11 | 6 | 1 |
| 2026-W13 | 1 | 1 |
| 2026-W15 | 1 | 1 |
| 2026-W16 | 1 | 1 |
| 2026-W18 | 1 | 1 |
| 2026-W19 | 2 | 2 |
| 2026-W24 | 5 | 3 |
| 2026-W30 | 1 | 1 |
| 2026-W36 | 1 | 1 |
| 2026-W37 | 1 | 1 |
| 2026-W38 | 1 | 1 |
| 2026-W39 | 1 | 1 |
| 2026-W40 | 4 | 3 |
In their words
If your data must remain on-premises, VectorAI DB provides the vector storage layer while enabling fast semantic retrieval within your own infrastructure.
It does not establish real semantic retrieval or correct answers.
Infino CEO Ekechi Nwokah tells The New Stack that agents are the “largest new consumer of data since the web browser”, but he laments that they are still “being served with a fragmented stack built for a different era,” i.e., data warehouses for SQL, search engines for keywords, vector databases for semantic search , and ETL pipelines to keep them all in sync.
But out in the wild, APIs time out, rate limits get hit, and semantic searches frequently return empty arrays.
This lets an application use graph patterns against current business data, then add semantic retrieval without turning every lookup into a reconciliation job across several stores.
Broad questions get semantic search grounded in graph context; factual lookups get exact answers from the graph.
RAG query rewriting is the practice of transforming a user's raw question into one or more reformulated queries before hitting the retriever, so semantic search returns passages the original phrasing would've missed.
Those edges are the join paths the agent follows: Neo4j browser Storing it as a graph is what makes retrieval work in two moves: semantic search finds an anchor table , then the graph pulls in the related tables and the exact columns to join on .