What problem does it solve? Turning PDFs, Markdown, HTML, and JSON into a queryable Neo4j knowledge graph requires coordinating chunking, LLM entity extraction, embeddings, and entity resolution, which is error-prone without a proven pipeline. ## Core Features & Use Cases - SimpleKGPipeline Setup: Configure neo4j-graphrag's SimpleKGPipeline with GraphSchema definitions, multiple LLM providers (OpenAI, Anthropic, Vertex AI, Ollama, Bedrock), and embedders to build Document→Chunk→Entity graph structures. - Chunking and Entity Resolution: Apply FixedSizeSplitter tuning guidance and run SinglePropertyExactMatchResolver, FuzzyMatchResolver, or SpaCySemanticMatchResolver to merge duplicate entities after ingestion. - Alternative Ingestion Paths: Use the no-code LLM Graph Builder web UI, apoc.load.json for semi-structured JSON, or LangChain/LlamaIndex document loaders connected to Neo4j. - Use Case: Ingest a folder of quarterly PDF reports into Neo4j, extract Person and Organization entities with GPT-4.1, resolve duplicates, and verify the resulting graph with Cypher queries. ## Quick Start Ask the agent to ingest a PDF file into Neo4j using SimpleKGPipeline with a defined entity schema and then verify the Document and Chunk node counts.