> ## Documentation Index
> Fetch the complete documentation index at: https://docs.experio.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Content Types

> Define document types and control how they are processed during ingestion

## Overview

Content types define the categories of documents your system processes and how the AI should classify and extract information from them. Each content type includes instructions for the AI on what entities and relationships to look for.

Navigate to **Admin > Data Sources > Content Types**.

## Viewing Content Types

The content types page lists all configured types with:

* Content type name
* Number of entity types associated
* Number of relationship types associated
* Created and last modified dates

## Creating a Content Type

Click **Create New** to define a new content type:

1. **Name** — A descriptive name for the document category (e.g., "Contracts", "Proposals", "Meeting Notes")
2. **Classification Instructions** — Guidance for the AI on how to identify documents of this type
3. **Entity Types** — Which entities to extract from these documents
4. **Relationship Types** — Which relationships to identify between extracted entities
5. **Metadata** — Additional configuration for processing

### Ingestion extraction policy

On the **Basic Information** tab, the **Ingestion extraction** section controls how deeply ingestion
uses LLMs for this content type:

* **Default mode** — `full`, `metadata_and_snippet`, or `metadata_only`
* **Primary model tier** — `large`, `medium`, or `small` for primary extraction
* **Validation pass** — optional secondary LLM pass (off by default for metadata-only Excel)
* **Excel overrides** — separate mode for spreadsheets

See [Extraction Policy](/admin-guide/extraction-policy) for mode behavior, system limits, and filter
overrides.

### Entity and relationship attributes

**Entity attributes** are chosen from the ontology per entity type. You select which attributes apply,
edit extraction instructions (defaults come from the ontology unless you override them), and set
whether an attribute is required.

**Relationship attributes** follow the same idea:

* Attributes available on a relationship come from the **ontology definition for that triple**
  (source entity type, relationship type, target entity type).
* You pick attributes from a dropdown — you do **not** type arbitrary names; **types** come from the
  ontology (shown read-only).
* **Extraction instructions** default from the ontology and can be overridden per content type for
  document-specific wording.

Relationship attributes are included in extraction prompts so the model can fill an `attributes`
object on each extracted edge when the document supports values.

See also: [Relationship attributes (architecture)](/architecture/relationship-attributes).

## Test Ingestion

The test ingestion feature lets you validate your content type configuration before processing real data.

1. Click **Test Ingestion** on any content type
2. Configure test parameters:
   * **Mode** — Choose between:
     * **Classify & Extract** — Full processing (classification + entity extraction)
     * **Classify Only** — Test document classification without extraction
     * **Extract Only** — Test entity extraction without classification
   * **Max Pages** — Limit pages to process (default: 3, use -1 for full document)
3. Upload a sample file
4. Review the results:

### Test Results

The test results display:

* **Classification Scores** — Confidence scores for each content type, with the selected type highlighted
* **Entities Table** — Extracted entities showing Type, Name, and Attributes
* **Relationships Table** — Extracted relationships showing Source, Type, Target, and **Attributes**
  (key/value pairs returned by extraction when present)
* **Raw JSON** — Full raw output for debugging

<Tip>
  Run test ingestion with representative documents before activating a content type in production. This helps fine-tune classification instructions and entity extraction rules.
</Tip>

## Editing Content Types

Click any content type to open its editor. Changes to a content type affect how future documents are processed — previously processed documents are not retroactively re-processed.