Developer

Ontology Builder

Map entities, owners, properties, and relationships in a visual canvas, then export a clean ontology JSON draft for your team.

4 Objects

3 relationships

0 issues

Ontology canvas

Select an entity to inspect or edit it.

75%

Ontology JSON

{
  "ontology": {
    "entities": [
      {
        "id": "customer",
        "name": "Customer",
        "type": "core",
        "owner": "RevOps",
        "properties": [
          {
            "id": "customer-id-1783860155028-0-24823617652826502",
            "name": "customer_id",
            "type": "string",
            "required": true,
            "description": "",
            "example": ""
          },
          {
            "id": "segment-1783860155028-0-1203725955106465",
            "name": "segment",
            "type": "string",
            "required": false,
            "description": "",
            "example": ""
          },
          {
            "id": "region-1783860155029-0-2859831342556909",
            "name": "region",
            "type": "string",
            "required": false,
            "description": "",
            "example": ""
          }
        ]
      },
      {
        "id": "account",
        "name": "Account",
        "type": "core",
        "owner": "Sales",
        "properties": [
          {
            "id": "account-id-1783860155029-0-00587944239662308",
            "name": "account_id",
            "type": "string",
            "required": true,
            "description": "",
            "example": ""
          },
          {
            "id": "arr-1783860155029-0-6306750670859169",
            "name": "arr",
            "type": "number",
            "required": false,
            "description": "",
            "example": ""
          },
          {
            "id": "industry-1783860155029-0-9654887131631504",
            "name": "industry",
            "type": "string",
            "required": false,
            "description": "",
            "example": ""
          }
        ]
      },
      {
        "id": "contract",
        "name": "Contract",
        "type": "event",
        "owner": "Legal",
        "properties": [
          {
            "id": "contract-id-1783860155029-0-7145056578744093",
            "name": "contract_id",
            "type": "string",
            "required": true,
            "description": "",
            "example": ""
          },
          {
            "id": "signed-at-1783860155029-0-6718805943454418",
            "name": "signed_at",
            "type": "date",
            "required": false,
            "description": "",
            "example": ""
          },
          {
            "id": "term-months-1783860155029-0-17151834862516413",
            "name": "term_months",
            "type": "number",
            "required": false,
            "description": "",
            "example": ""
          }
        ]
      },
      {
        "id": "product",
        "name": "Product",
        "type": "reference",
        "owner": "Data",
        "properties": [
          {
            "id": "sku-1783860155029-0-9111701765410529",
            "name": "sku",
            "type": "string",
            "required": true,
            "description": "",
            "example": ""
          },
          {
            "id": "family-1783860155029-0-821001179762916",
            "name": "family",
            "type": "string",
            "required": false,
            "description": "",
            "example": ""
          },
          {
            "id": "margin-band-1783860155029-0-9912097187782858",
            "name": "margin_band",
            "type": "string",
            "required": false,
            "description": "",
            "example": ""
          }
        ]
      }
    ],
    "relationships": [
      {
        "id": "rel-1",
        "from": "customer",
        "to": "account",
        "label": "owns",
        "category": "owns",
        "cardinality": "one_to_many",
        "description": "",
        "allowSelf": false
      },
      {
        "id": "rel-2",
        "from": "account",
        "to": "contract",
        "label": "signs",
        "category": "references",
        "cardinality": "one_to_many",
        "description": "",
        "allowSelf": false
      },
      {
        "id": "rel-3",
        "from": "contract",
        "to": "product",
        "label": "covers",
        "category": "references",
        "cardinality": "many_to_one",
        "description": "",
        "allowSelf": false
      }
    ],
    "layout": {
      "canvas": {
        "width": 1120,
        "height": 680
      },
      "nodes": {
        "customer": {
          "x": 92,
          "y": 95
        },
        "account": {
          "x": 362,
          "y": 70
        },
        "contract": {
          "x": 620,
          "y": 186
        },
        "product": {
          "x": 260,
          "y": 290
        }
      }
    }
  }
}

Import ontology

Upload JSON

What is an ontology builder?

An ontology builder helps teams define the important entities in a domain and how those entities relate to each other. Instead of starting with database tables, it starts with shared language: customers, accounts, contracts, products, events, owners, and properties. This makes it useful for product planning, data catalogs, knowledge graphs, analytics requirements, and AI retrieval systems where consistent terminology matters.

How to build an ontology

1
Add the core entities
Create the main nouns in your domain, such as Customer, Account, Product, Subscription, or Ticket.
2
Assign owners and types
Mark each entity as core, event, or reference data, then record the team responsible for maintaining it.
3
List important properties
Add identifiers and common fields so downstream teams understand what belongs on each entity.
4
Connect relationships
Define how entities connect, such as customer owns account or contract covers product.
5
Export the JSON
Copy the generated JSON into a data catalog, design document, ticket, or repository.

Output structure

ontology:
  entities:
    - id
      name
      type
      owner
      properties[]
  relationships:
    - from
      to
      label

The export is intentionally small and portable. Each entity keeps a stable id, display name, type, owner, and property list. Each relationship references entity ids so the graph can be imported into another tool or versioned in Git.

Reference: W3C - Semantic Web

Examples

Use case	Ontology draft
SaaS billing model	Customer, Account, Contract, Product, Invoice Clarifies ownership between RevOps, Sales, Legal, and Data.
Support analytics	Ticket, Agent, Customer, Product, Resolution Event Makes reporting fields and event relationships explicit.
AI retrieval taxonomy	Document, Topic, Source, Author, Claim Useful when planning metadata for search and retrieval systems.

Common use cases

Drafting a domain model before database design
Documenting entity ownership across business teams
Planning a data catalog or semantic search index
Aligning product, analytics, and engineering terminology
Creating a lightweight knowledge graph seed file
Explaining relationships in a technical design review

Related tools

Formatador JSON

Formate, valide e minifique JSON com relatórios precisos de linha e coluna de erro.

CSV Combiner & Analyzer

Drop multiple CSV files, validate matching headers, merge the rows, analyze columns, and download one clean file.

Metrics Dictionary

Define business terms, metric owners, synonyms, formulas, and approval status before mapping them into a semantic layer.

Semantic Layer Builder

Model datasets, dimensions, measures, joins, and SQL previews for analytics teams before committing to code.

Frequently asked questions

Is this a full ontology editor?

No. It is a lightweight planning tool for sketching entities and relationships quickly. Use the JSON export as a starting point for a formal ontology, data catalog, or knowledge graph workflow.

Does the data leave my browser?

No. The canvas state is kept locally in the page and the export is generated in your browser.

What should count as an entity?

Use entities for concepts that have their own identity, lifecycle, owner, or repeated references across systems. Simple attributes usually belong in the properties list instead.

Can I version the output?

Yes. The JSON is plain text, so it can be pasted into documentation, checked into Git, or transformed by your own scripts.

Last updated 2026-06-14

{ "ontology": { "entities": [ { "id": "customer", "name": "Customer", "type": "core", "owner": "RevOps", "properties": [ { "id": "customer-id-1783860155028-0-24823617652826502", "name": "customer_id", "type": "string", "required": true, "description": "", "example": "" }, { "id": "segment-1783860155028-0-1203725955106465", "name": "segment", "type": "string", "required": false, "description": "", "example": "" }, { "id": "region-1783860155029-0-2859831342556909", "name": "region", "type": "string", "required": false, "description": "", "example": "" } ] }, { "id": "account", "name": "Account", "type": "core", "owner": "Sales", "properties": [ { "id": "account-id-1783860155029-0-00587944239662308", "name": "account_id", "type": "string", "required": true, "description": "", "example": "" }, { "id": "arr-1783860155029-0-6306750670859169", "name": "arr", "type": "number", "required": false, "description": "", "example": "" }, { "id": "industry-1783860155029-0-9654887131631504", "name": "industry", "type": "string", "required": false, "description": "", "example": "" } ] }, { "id": "contract", "name": "Contract", "type": "event", "owner": "Legal", "properties": [ { "id": "contract-id-1783860155029-0-7145056578744093", "name": "contract_id", "type": "string", "required": true, "description": "", "example": "" }, { "id": "signed-at-1783860155029-0-6718805943454418", "name": "signed_at", "type": "date", "required": false, "description": "", "example": "" }, { "id": "term-months-1783860155029-0-17151834862516413", "name": "term_months", "type": "number", "required": false, "description": "", "example": "" } ] }, { "id": "product", "name": "Product", "type": "reference", "owner": "Data", "properties": [ { "id": "sku-1783860155029-0-9111701765410529", "name": "sku", "type": "string", "required": true, "description": "", "example": "" }, { "id": "family-1783860155029-0-821001179762916", "name": "family", "type": "string", "required": false, "description": "", "example": "" }, { "id": "margin-band-1783860155029-0-9912097187782858", "name": "margin_band", "type": "string", "required": false, "description": "", "example": "" } ] } ], "relationships": [ { "id": "rel-1", "from": "customer", "to": "account", "label": "owns", "category": "owns", "cardinality": "one_to_many", "description": "", "allowSelf": false }, { "id": "rel-2", "from": "account", "to": "contract", "label": "signs", "category": "references", "cardinality": "one_to_many", "description": "", "allowSelf": false }, { "id": "rel-3", "from": "contract", "to": "product", "label": "covers", "category": "references", "cardinality": "many_to_one", "description": "", "allowSelf": false } ], "layout": { "canvas": { "width": 1120, "height": 680 }, "nodes": { "customer": { "x": 92, "y": 95 }, "account": { "x": 362, "y": 70 }, "contract": { "x": 620, "y": 186 }, "product": { "x": 260, "y": 290 } } } } }

What is an ontology builder?

How to build an ontology

Add the core entities

Create the main nouns in your domain, such as Customer, Account, Product, Subscription, or Ticket.

Assign owners and types

Mark each entity as core, event, or reference data, then record the team responsible for maintaining it.

List important properties

Add identifiers and common fields so downstream teams understand what belongs on each entity.

Connect relationships

Define how entities connect, such as customer owns account or contract covers product.

Export the JSON

Copy the generated JSON into a data catalog, design document, ticket, or repository.