neo4j-document-import-skill

Ingest PDFs and text into Neo4j knowledge graphs via SimpleKGPipeline.

101|35|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/neo4j-contrib/neo4j-skills --skill neo4j-document-import-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: neo4j-document-import-skill
Source: https://github.com/neo4j-contrib/neo4j-skills/tree/main/neo4j-document-import-skill
Command: npx skills add https://github.com/neo4j-contrib/neo4j-skills --skill neo4j-document-import-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Neo4j document ingestion typically requires significant manual effort to chunk content and model extracted entities and relationships; this Skill guides agents through converting PDFs and text into a connected knowledge graph for graph and GraphRAG-style workloads.

Core Features & Use Cases

  • Document chunking to graph nodes: Splits input documents into :Document and :Chunk structures suitable for downstream retrieval and traversal.
  • LLM-driven entity and relationship extraction: Uses SimpleKGPipeline (neo4j-graphrag) and related components to turn text into typed entities/edges.
  • Flexible ingestion options: Supports semi-structured JSON loading via apoc.load.json, and provides a no-code alternative via Neo4j LLM Graph Builder.
  • Graph schema & resolution guidance: Helps define a schema, run entity resolution, and set constraints/indexes for reliable ingestion.

Quick Start

Tell the agent to ingest a file like report.pdf into Neo4j using SimpleKGPipeline with a defined GraphSchema, chunking, embeddings storage, and post-ingestion entity resolution.

Frequently Asked Questions about neo4j-document-import-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ingest unstructured PDF documents into a Neo4j knowledge graph?

To ingest unstructured PDF documents into a Neo4j knowledge graph, use SimpleKGPipeline to chunk content into Document and Chunk structures, then extract typed entities and relationships via LLM. Configure a defined GraphSchema to drive schema-driven extraction and store embeddings for graph workloads.

What is the best way to load semi-structured JSON data into Neo4j for GraphRAG workflows?

Loading semi-structured JSON data into Neo4j for GraphRAG workflows uses `apoc.load.json` for flexible ingestion. After loading, SimpleKGPipeline extracts entities and relationships from the content using a defined schema, creating connected graph structures suitable for retrieval-augmented generation.

How does LLM entity extraction work when building a knowledge graph from text?

LLM entity extraction for building a knowledge graph from text works by processing chunked Document and Chunk structures through SimpleKGPipeline. The pipeline uses a configured GraphSchema to identify and map typed entities and edges, applying entity resolution to merge duplicates and ensure reliable graph ingestion.

Can I use LangChain document loaders to import text into Neo4j?

Yes, you can use LangChain document loaders to import text into Neo4j. The ingestion workflow supports LangChain and LlamaIndex document-loader integrations, allowing you to pass unstructured text directly to SimpleKGPipeline for chunking, LLM-driven extraction, and graph node creation.

Do I need a no-code tool to extract entities from Markdown files into Neo4j?

You do not strictly need a no-code tool to extract entities from Markdown files, as SimpleKGPipeline supports programmatic ingestion. However, Neo4j LLM Graph Builder is available as a no-code alternative for users who want to visually ingest Markdown and text documents into a knowledge graph without writing code.

What are the limitations of using SimpleKGPipeline for document ingestion in Neo4j?

Limitations of SimpleKGPipeline for document ingestion include its focus on unstructured and semi-structured text rather than structured CSV imports. It handles extraction and entity resolution but avoids retrieval, vector indexing, and structured CSV import responsibilities, which are managed by other specialized skills.