Entities & Relationships
Understanding entity types and relationship patterns in the Knowledge Graph
Entities & Relationships
This page explains how entities and relationships are extracted, stored, and used in AgentisPro RAG Engine.
Entity Extraction Process
When you upload a document, the following happens:
Entity Types
Person 👤
Individuals mentioned in documents.
| Property | Description | Example |
|---|---|---|
name | Full name | "John Smith" |
role | Job title (if found) | "CEO" |
email | Email address | "john@acme.com" |
source_doc | Origin document | "org_chart.pdf" |
Extraction triggers:
- Proper nouns followed by roles ("John Smith, CEO")
- Email patterns
- Signature blocks
- Author metadata
Organization 🏢
Companies, departments, teams.
| Property | Description | Example |
|---|---|---|
name | Organization name | "Acme Corporation" |
type | Sub-type | "Company", "Department" |
industry | Sector (if found) | "Technology" |
Extraction triggers:
- Legal suffixes (Inc., LLC, Corp.)
- Department keywords ("Sales Team", "HR Department")
- Domain names in emails
Product 📦
Products, services, features.
| Property | Description | Example |
|---|---|---|
name | Product name | "Widget Pro" |
version | Version number | "2.1.0" |
category | Product type | "Software" |
Extraction triggers:
- Product naming patterns
- Version numbers
- SKU codes
- Trademark symbols (™, ®)
Location 📍
Physical and virtual places.
| Property | Description | Example |
|---|---|---|
name | Location name | "New York Office" |
type | Location type | "Office", "Region" |
address | Full address | "123 Main St" |
Extraction triggers:
- Address patterns
- City/country names
- Building names
- Geographic references
Event 📅
Meetings, deadlines, milestones.
| Property | Description | Example |
|---|---|---|
name | Event name | "Q4 Planning" |
date | Event date | "2026-01-15" |
type | Event type | "Meeting", "Deadline" |
Extraction triggers:
- Date patterns
- Event keywords ("meeting", "conference", "deadline")
- Calendar references
Concept 💡
Abstract ideas, topics, categories.
| Property | Description | Example |
|---|---|---|
name | Concept name | "Data Privacy" |
category | Topic area | "Compliance" |
Extraction triggers:
- Repeated themes across documents
- Section headers
- Tag-like patterns
Relationship Types
Common Relationships
| Relationship | From | To | Example |
|---|---|---|---|
works_at | Person | Organization | John → Acme |
manages | Person | Person | Sarah → John |
authored | Person | Document | Jane → Report |
mentions | Document | Entity | Contract → Acme |
part_of | Entity | Entity | Widget → Product Line |
located_in | Entity | Location | Office → New York |
occurred_on | Event | Date | Meeting → 2026-01-15 |
related_to | Entity | Entity | Topic A → Topic B |
Relationship Properties
Relationships can have properties:
| Property | Description |
|---|---|
since | Start date |
until | End date |
role | Role in relationship |
strength | Confidence score (0-1) |
source | Origin document |
Entity Linking
When the same entity appears in multiple documents, AgentisPro links them:
Linking Algorithm
- Exact match: Same name → 100% match
- Fuzzy match: Similar names → Calculate similarity
- Context match: Same relationships → Increase confidence
- User override: Manual linking/unlinking
Creating Entities Manually
Via Web UI
- Navigate to Knowledge Graph
- Click + Add Entity
- Fill in properties:
- Name (required)
- Type (required)
- Custom properties
- Save
Via API
Creating Relationships Manually
Via Web UI
- Select source entity
- Click + Add Relationship
- Search for target entity
- Select relationship type
- Add properties (optional)
- Save
Via API
Editing Entities
Merge Duplicates
If the same entity was created twice:
- Select both entities (Ctrl+Click)
- Right-click → Merge Entities
- Choose primary entity (keeps properties)
- Confirm
Split Entity
If different entities were incorrectly merged:
- Select entity
- Click Edit → Split
- Define which relationships go to each new entity
- Confirm
Best Practices
Naming Conventions
| Type | Convention | Example |
|---|---|---|
| Person | Full name, title case | "John Smith" |
| Organization | Official name | "Acme Corporation" |
| Product | Brand name + version | "Widget Pro 2.0" |
Relationship Consistency
Use consistent relationship types:
- ✅
works_at(notemployed_by,works_for) - ✅
authored(notwrote,created) - ✅
manages(notsupervises,leads)
Quality Control
Regular maintenance:
- Review new entities weekly
- Merge duplicates
- Delete false positives
- Add missing relationships