Why Use an Ontology?
Most organizations store critical information across dozens of tools — CRMs, spreadsheets, documents, emails. The Ontology brings this scattered data into a single, coherent model that both humans and AI agents can work with.Structured Knowledge
Define the entities and relationships that matter to your business with typed properties and validation rules.
AI-Native
Athena agents can read, create, and update ontology data in conversations — no manual data entry required.
Connected Data
Link related entities together to capture how your data connects, enabling richer queries and insights.
Core Concepts
The Ontology is built from three primitives. If you’re familiar with databases, the analogy is straightforward:| Ontology Concept | Database Equivalent | Description |
|---|---|---|
| Object Type | Table | A template defining a category of real-world entity (e.g., “Deal”, “Client”) |
| Instance | Row | A single record of an object type (e.g., the deal “Acme Series B”) |
| Relationship | Foreign key / Join | A named, typed link between two object types (e.g., Deal → assigned_to → Person) |
Object Types
An object type is the schema definition for a category of entity. For example, a “Company” object type might have properties likename, industry, employee_count, and annual_revenue. Every instance of the “Company” type will have these same properties.
Properties
Properties define the attributes of an object type. Each property has a name, a type, and optional constraints:| Type | Description | Example |
|---|---|---|
| Text | Free-form string | Name, email, notes |
| Number | Decimal value | Revenue, price, latitude |
| Integer | Whole number | Employee count, quantity |
| Boolean | True/false | Is active, is verified |
| Date | Calendar date | Start date, founded year |
| Enum | Fixed set of options | Stage, status, tier |
Relationships
Relationships define how object types connect to each other. Each relationship has:- Source and target object types
- A name describing the relationship (e.g., “assigned_to”, “works_at”, “owns”)
- Cardinality: one-to-one, one-to-many, many-to-one, or many-to-many
- Directionality: whether the relationship goes one way or both
How Agents Use the Ontology
Once you’ve defined your ontology, Athena agents can work with it directly:- Create instances — “Log a new deal: Acme Series B, $5M, closing next quarter”
- Query data — “Show me all deals in the negotiation stage worth over $1M”
- Update records — “Move the Acme deal to closed-won and update the value to $5.5M”
- Traverse relationships — “Who owns the deals connected to Acme Corp?”
Getting Started
Open the Ontology Builder
Navigate to Experimental → Ontology Builder from the sidebar. This is the visual workspace for defining your data model.
Create your first object type
Click New Object Type or double-click the canvas. Choose a template or start from scratch. Define properties and set a title property.
Add relationships
Drag from the handle on one object type node to another to create a relationship. Configure the name, cardinality, and direction.

