Nicheloom visits: 58,069 all-time · 7,637 in the last 7 days

The opportunity tracker for new startups.

Today: 1,953 launches · Niche of the day: specialized calculation tools · See what launched today →

Ontology-driven knowledge graph extraction from text

Get picks like this daily. Today's launch numbers, the top launches, AI and tech news, and a daily opportunity pick, straight to your inbox.

Want to reach these readers? Sponsor an issue.

TrustGraph now supports automatic knowledge graph construction guided by OWL ontologies. You provide an ontology (OWL/Turtle format or build one in the Workbench editor), point it at your documents, and it extracts entities and relationships that conform to your schema.The problem this solves: generic GraphRAG approaches extract whatever relationships an LLM thinks are relevant, which often misses domain-specific semantics. If you're working in healthcare, finance, or intelligence analysis, you likely already have ontologies (or can adapt standards like SOSA, FIBO, etc.) that define what matters. TrustGraph uses these to constrain extraction, so the resulting graph reflects your domain model rather than the LLM's interpretation.How it works: The ontology defines classes and properties. During extraction, the LLM is prompted to identify instances of those classes and relationships matching those properties. The output is validated against the schema before being written to the graph store.Built on Apache Pulsar for scalability, supports multiple graph backends (Memgraph, FalkorDB, others), and runs locally or in cloud. Apache 2.0 licensed.Repo: https://github.com/trustgraph-ai/trustgraphOntology RAG docs: https://docs.trustgraph.ai/guides/ontology-rag/Happy to answer questions about the extraction approach or architecture.

HN · launched Nov 24, 2025 · 13 upvotes (top 42%) · 1 view

Niche: knowledge base and graph software · 107 launches, 1 in the last 7 days · Explore this niche →

Category and tags

  • Horizontal
  • Data infrastructure
  • Developer
  • AI-native
  • Hobby / open-source project

Source listing ↗

Could you build this?

Partial The UI and standard LLM prompting for entity extraction can be vibe-coded, but robustly enforcing complex OWL schema constraints, validation, and semantic reasoning requires specialized knowledge engineering.

What it would actually take: The architecture requires an ontology parser (e.g., Apache Jena, rdflib), an LLM extraction pipeline using constrained decoding or grammar-guided generation, and an RDF triple store (such as Neo4j or Ontotext GraphDB). The hard technical problem is automated entity alignment, coreference resolution, and strict OWL-DL consistency checking against ontological axioms without hallucinating relations. This requires background in formal knowledge representation, Semantic Web standards (RDF/OWL/SHACL), and advanced graph data modeling.

Discussion

No comments on this launch.

Competitors

Other products that read as similar to this one : 156 launches clear the similarity bar, closest 8 shown.

Attention rank: #69 of 157 (itself plus its competitors, highest first, normalized so YC and Product Hunt are compared fairly).

Launched 26 days after the earliest competitor.

The niche, labels, vibe code rating and competitor comparison on this page are analysis by Nicheloom. If you use them, please credit nicheloom.com. How you may use our data.