OntoCast

Agentic ontology-assisted extraction of RDF knowledge graphs from documents.

OntoCast turns unstructured text into queryable RDF: it co-evolves domain ontologies and fact graphs in a parallel map/reduce pipeline, with RDF 1.2 provenance, entity disambiguation across chunks, and optional vector-backed ontology retrieval. Run it as a REST service, a batch CLI, or embed the pipeline in your own LangChain / LangGraph agent.

Documentation: growgraph.github.io/ontocast

Why OntoCast

Most extractors dump triples and leave ontology drift to you. OntoCast treats schema and instance data as one loop: per-chunk render → critic → merge, with GraphUpdate patches (insert/delete) instead of regenerating whole graphs, SHACL validation with LLM-free autofix, and a light install so you can embed the core without pulling Docling, gRPC, or ONNX.

Features

• Parallel ontology + facts loops — concurrent per-unit render/critic with configurable workers
• GraphUpdate patches — token-efficient insert/delete ops, not full-graph regeneration
• Entity disambiguation — embedding + symbolic alignment across chunks
• RDF 1.2 provenance — quoted triples / provenance artifacts; optional strip_provenance
• Ontology context — catalog selection, vector retrieval (LanceDB or Qdrant), or a fixed ontology
• Facts validation — invariants, SHACL, and machine repairs without an extra LLM pass
• Stores — in-memory pyoxigraph by default; Fuseki for persistence; tenancy by tenant/project
• LLM caching — disk cache, in-flight limits, optional read-only / batch pre-warm
• Embeddable — ontocast_tools, run_unit_pipeline, or a LangGraph node

Install

Pick at least one LLM provider extra. Add server for the CLI and HTTP API:

uv add "ontocast[server,openai]"
# or: pip install "ontocast[server,openai]"

Common add-ons: doc-processing (PDF/DOCX), lancedb or qdrant (ontology retrieval), shacl (shape validation).

uv add "ontocast[server,openai,doc-processing,lancedb,shacl]"

Full extras table: Installation.

Quick start

cp .env.example .env
# Set LLM_API_KEY (and LLM_PROVIDER / LLM_MODEL_NAME as needed)

ontocast serve
curl -X POST http://localhost:8999/process -F "file=@document.pdf"

Batch without a server:

ontocast process --input-path ./document.pdf --head-chunks 5 --output-dir ./out

Omit FUSEKI_URI for in-memory pyoxigraph. Details: Quick Start.

Supplying Your Ontologies

OntoCast uses seed ontologies (in Turtle .ttl format) to guide extraction. Provide yours in two ways:

1. Directory Seed: Set ONTOCAST_ONTOLOGY_DIRECTORY=/path/to/your/ontologies in your .env. All .ttl files in that folder sync automatically on startup.
2. API Upload: Register schemas dynamically with the running server:

   curl -X POST