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

# Entities

> All entity types that Adapter extracts and resolves from your connected data sources

Adapter promotes recurring real-world things — people, companies, reservations, documents — into **entities**. Each entity has a fixed schema, a stable id, and is resolved across every evidence source it appears in.

Entities are derived from evidence. A single person mentioned in an email, a calendar event, and a Slack message resolves to one `person` entity, with each mention preserved as a citation.

Citations returned by [Ask](/api-reference/knowledge/ask) carry a `type` naming the kind of record each cited row is. Reservation entities are cited under a single `reservation` type, with the specific kind (one of the values below) in the row's `reservation_type` field.

```json All entity_type values theme={null}
[
  "actor",
  "document",
  "file",
  "organization",
  "person",
  "purchase",
  "reservation"
]
```

```json All reservation_type values theme={null}
[
  "car_rental",
  "dining",
  "event_reservation",
  "flight",
  "hotel_stay",
  "train"
]
```

## All entity types

| Entity Type    | Description                                                                                                                      |
| -------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| `actor`        | A non-person participant in communication: a shared address that fans out to people, an automated sender, or a bookable resource |
| `document`     | Searchable document/file entity with semantic search capabilities                                                                |
| `file`         | A file or document ingested from a source system (Drive, Notion, attachments, etc.)                                              |
| `organization` | Organization/company extracted from evidence                                                                                     |
| `person`       | Individual person extracted from evidence                                                                                        |
| `purchase`     | Purchase/transaction entity                                                                                                      |
| `reservation`  | A booking extracted from a confirmation email — the specific kind is in `reservation_type`                                       |

### Reservation kinds

Subtypes of `reservation`, carried in its `reservation_type` field:

| `reservation_type`  | Description                                                                                                                                                              |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `car_rental`        | Car rental reservation entity data                                                                                                                                       |
| `dining`            | Restaurant reservation entity data                                                                                                                                       |
| `event_reservation` | Event/ticket reservation entity data                                                                                                                                     |
| `flight`            | Flight reservation entity representing a single itinerary (one-way, round-trip, or multi-city) with one or more legs, each containing one or more segments (connections) |
| `hotel_stay`        | Hotel reservation entity data                                                                                                                                            |
| `train`             | Train reservation entity data                                                                                                                                            |

## What each entity carries

The summaries below describe the information you can expect each entity type to carry. Attributes may be added or removed in future releases.

### Reservation

All bookings surface as a single **`reservation`** entity, with the specific kind in the `reservation_type` field. Every reservation carries the booking essentials when present: a confirmation code, the provider, start and end times (in the venue's local timezone), a location, the named guests or travelers, the price, and the booking status. Each kind adds its own detail on top:

* `car_rental` — Rental company, pickup and drop-off times and locations, vehicle class, renter name, and total price.
* `dining` — Restaurant name and location, reservation time, party size, the name on the reservation, and cuisine type.
* `event_reservation` — Event name, venue and address, start/end times, attendee name, seat or section, ticket count, and total price.
* `flight` — The full itinerary: airline, flight numbers, departure/arrival airports and times for every leg and connection, every passenger on the booking, trip type (one-way, round-trip, multi-city), and total price.
* `hotel_stay` — Property name and address, check-in/check-out times, guest name, room type, number of nights, and total price.
* `train` — Operator, departure and arrival stations and times, passenger name, seat and travel class, and ticket price.

### Document

Title, document type, searchable text content with a preview, and file metadata (format, size, source location).

### Organization

Name and legal name, web domain, contact details, address, industry, parent organization, and public identifiers when available.

### Person

Names (including given/family name variants), email addresses, phone numbers, job title, employer and other affiliations, linked profiles, and when they were first and last seen in your data.

### Purchase

Order number, seller, line items, total amount and currency, order and delivery dates, fulfillment type, and tracking number.