The challenge. The approach.

Architected and implemented a GraphRAG (Graph-based Retrieval-Augmented Generation) system for an industrial automation client in the packaging sector. The system integrates a knowledge graph (Neo4j) with LLM-powered retrieval to answer complex technical queries across thousands of process and maintenance documents.

My scope covered the document-to-graph data flow, embedding and indexing pipelines, and orchestration of retrieval and generation in LangGraph. The system brings retrieved subgraphs and document context into the LLM’s answer generation, rather than relying on the model’s parametric knowledge alone.

The technical focus was making connected information usable: organizing process knowledge in Neo4j, retrieving relevant context for a technical question, and retaining the source lineage needed to inspect an answer. That traceability supports review, troubleshooting, and compliance workflows without implying that a generated answer is automatically correct.

Inside the system.

Graph-grounded retrieval

Neo4j subgraphs and document context supply the evidence for technical answers.

Orchestrated generation

LangGraph connects the retrieval and generation stages into an explicit workflow.

Source traceability

Document ingestion, embeddings, and indexing preserve a route back to the underlying source.

From input to impact.

DocumentsChunking & embeddingNeo4j graphSubgraph retrievalLLM answer

Data flow: ingestion (documents → graph) and query (user question → retrieval → LLM → answer).

The technical foundation.

Python3.11LangGraph0.2Neo4j5.xOpenAI APIgpt-4oAzure OpenAIembedding-3Next.js15

Technologies reflect the original project. Outcomes are reported from the existing portfolio; client-identifying details are withheld.

Where I would explore next.

These are potential research and engineering extensions, not methods claimed as implemented in this project or additional measured outcomes.

Hybrid, multi-hop retrieval

Evaluate vector and lexical retrieval with graph traversal for questions spanning multiple connected entities.

Neurosymbolic constraints

Explore ontology-aware query validation and domain rules around LLM-generated graph queries.

Evidence-based evaluation

Benchmark retrieval coverage, citation faithfulness, and answer quality on domain-specific questions.

Back to selected work Explore the next project
A GOOD PLACE TO START

What are you
thinking about?

A difficult problem. An ambitious idea. A team that needs a senior mind. Let’s connect.

I’m interested in

Opens a draft in your email app. Nothing is submitted or stored on this website.

Prefer a call? Book a time

Paolo’s personal AI

A first connection. Not a replacement for one.

A little transparency
before we talk.

This assistant answers questions about my experience, projects, and working together. Your messages and recent conversation are sent to Google Gemini only when you choose to send them.

Please don’t share confidential or sensitive information. AI answers can be mistaken; confirm important details with me.

How your data is handled