Skip to main content

Pre-built schemas for 17 real-world verticals

Domain Ontologies

A blank knowledge graph doesn’t know what an “Account” or a “Patient” or a “Shipment” is. Domain ontologies fix that before you write a single line of extraction code.

Each of ZeroDB’s 17 domain ontology templates is a real set of entity types, relationships, and properties for a specific vertical — finance, healthcare, legal, HR, IoT, software, and more. Apply one to a project and Context Graph immediately knows how to classify, extract, and link the entities that actually show up in that domain’s data.

The shared base model

Every domain extends POLE+O

POLE+O is an intelligence-analysis ontology — Person, Organization, Location, Event, and the +O extension, Object. All 17 domain templates declare their entity types as subtypes of one of these five categories, so a Finance Account and a Healthcare Patient share the same underlying graph structure even though they mean very different things.

Person

Human individual — employee, customer, patient, developer, etc.

Organization

Company, agency, department, or any organized group

Location

Physical address, region, facility, or logical location

Event

Time-bounded occurrence — meeting, incident, transaction, etc.

Object

Tangible or intangible thing — document, device, artifact, concept (the +O extension)

All 17 templates

Pick a vertical

Each card lists a sample of the real entity types defined in that domain’s template — every one of them ships with full relationship types, properties, and GLiNER extraction config.

Finance

Finance domain ontology for portfolio and compliance agent memory

AccountTransactionPortfolioSecurityCounterpartyFund

Healthcare

Healthcare domain ontology for medical agent memory

PatientProviderDiagnosisTreatmentMedication

Legal

Legal domain ontology for case management and litigation agent memory

CasePartyCounselRulingStatuteEvidence

HR

HR ontology for workforce management and recruiting agent memory

EmployeeCandidatePositionDepartmentPerformanceReview

IoT

IoT ontology for device management and sensor data agent memory

DeviceSensorGatewayReadingAlert

Software

Software engineering ontology for development workflow agent memory

RepositoryIssuePullRequestDeveloperServiceDeployment

Customer Success

Customer success ontology for support and retention agent memory

CustomerTicketSubscriptionAgentFeedback

DevOps

DevOps ontology for infrastructure and incident management agent memory

ServiceClusterDeploymentIncidentRunbook

E-Commerce

E-commerce ontology for shopping and order management agent memory

BuyerOrderProductSellerReviewCart

Education

Education ontology for learning management and tutoring agent memory

StudentInstructorCourseAssignmentInstitution

Insurance

Insurance ontology for policy and claims management agent memory

PolicyholderPolicyClaimAdjusterCoverageUnderwriter

Media

Media ontology for content management and publishing agent memory

ArticleAuthorPublicationCampaignAsset

Real Estate

Real estate ontology for property management and brokerage agent memory

PropertyListingBuyerSellerTransaction

Research

Research ontology for academic literature and experiment tracking agent memory

PaperAuthorDatasetExperimentGrant

Sales

Sales CRM ontology for pipeline and deal management agent memory

LeadAccountOpportunityContactCompetitor

Supply Chain

Supply chain ontology for logistics and procurement agent memory

SupplierWarehouseShipmentPurchaseOrderManufacturer

Travel

Travel ontology for booking and itinerary management agent memory

TravelerBookingFlightHotelDestination

Templates API

List, then apply

GET /templates lists every available semantic data product template — no authentication required, since templates are static definitions. Filter with category (general, domain, ontology_tier1, ontology_tier2, ontology_tier3).

List domain templates, then apply one
curl https://api.ainative.studio/api/v1/public/memory/v2/graph/templates?category=domain

# 200 OK
{
  "templates": [
    { "key": "finance", "description": "Finance domain ontology for portfolio and compliance agent memory" },
    { "key": "healthcare", "description": "Healthcare domain ontology for medical agent memory" },
    ...
  ],
  "total": 17
}

curl -X POST "https://api.ainative.studio/api/v1/public/memory/v2/graph/templates/finance/apply?project_id=$PROJECT_ID" \
  -H "Authorization: Bearer $TOKEN"

# 200 OK — Account, Transaction, Portfolio, Security, Counterparty, Fund,
# RiskAssessment, and ComplianceReport entity types are now registered
# as this project's ontology.

Manage a project’s ontology directly

GET /ontology?project_id=Get a project’s active entity types, predicates, constraints, and version
POST /ontologyCreate or update a project’s ontology — version auto-increments on every update

Go deeper

See how templates fit into Context Graph

Domain ontologies are one piece of Context Graph — entity extraction, knowledge graph storage, GraphRAG, and decision traces all build on the entity types a template registers.