RES

    Research Dashboard

    Deep dives into the two research projects driving my current work — hierarchical ANN quantization and knowledge-graph-augmented retrieval.

    R1 · Vector Retrieval

    Reusable Codebooks for Two-Tier ANN Retrieval

    Two-tier ANN pipelines train two independent Product Quantization codebooks — one for the cheap prefilter, one for the expensive reranker — duplicating storage and training cost. Can a single nested codebook serve both tiers?

    −1300×
    Training Overhead
    +2.2%
    R@1 vs PQ (GloVe)
    200 / 1536 / 3072
    Embedding dims
    3
    Nesting strategies

    Recall@1 across methods & datasets

    Nested Top-Down matches or beats unconstrained baselines.

    Index construction cost (relative)

    Shared codebooks collapse two trainings into one — up to 1300× cheaper.

    Recall@1 across all methods and datasets.
    Recall@1 across all methods and datasets.
    Bottom-Up · Top-Down · Middle-Anchor nesting.
    Bottom-Up · Top-Down · Middle-Anchor nesting.
    Middle-anchor Lloyd-Max nested codebooks.
    Middle-anchor Lloyd-Max nested codebooks.

    Key Insight

    Top-down decimation matches unconstrained TurboQuant within ±0.005 R@1 on all three datasets and beats PQ + reranking by +2.2 R@1 on GloVe-200 — using one shared codebook instead of two, with 50–1300× faster index construction. Bottom-up degrades by up to 12 points.

    Limitations

    Nesting forces an MSE redistribution: no nested family reaches zero penalty at two bit-widths at once, so low-bit tiers (b=2) pay a measurable cost. Data-oblivious codebooks lose ground to PQ on heavily anisotropic, high-dimensional corpora. Paper in prep (advisor: Prof. Ainesh Bakshi).

    R2 · Knowledge-Graph RAG

    Erica – LLM Knowledge Graph Reasoning

    repo

    Pure vector-based retrieval produces hallucinated or incoherent answers lacking structured reasoning paths.

    5,200+
    KG Nodes
    13.4k
    Relations
    −38pp
    Hallucination ↓
    Neo4j + Vectors
    Backend

    Knowledge graph growth

    LLM-driven semantic extraction over five pipeline stages.

    Vector-only vs Graph-augmented RAG

    Explicit reasoning paths dominate on faithfulness & hallucination.

    Erica pipeline

    UnstructuredSourcesLLM SemanticExtractionConcepts +PrerequisitesNeo4j KG+ EmbeddingsGraph-augmentedAnswer

    Key Insight

    Graph-augmented retrieval provides explicit reasoning paths that vector similarity alone cannot capture, measurably improving consistency over pure vector retrieval.

    Limitations

    Knowledge graph construction from unstructured sources requires careful schema design. Long-form outputs need asynchronous execution pipelines.