Core components
The Knowledge Layer is built on four primary components.Entities
An entity is a structured representation of a person, organization, topic, or event extracted from source documents. Each entity includes:- Structured attributes (for example, names, roles, or affiliations)
- Citations that link attributes back to source documents
Protocols
Protocols are defined sets of instructions, rules, or structured content associated with a matter. Protocols are indexed and embedded into the Knowledge layer so they can inform retrieval‑augmented generation (RAG) processes. The Knowledge layer stores protocol‑related information such as:- Protocol summaries
- Session breakdowns
- Extracted entities
- Additional protocol metadata or structured details
Metadata
Metadata provides descriptive context that supports reasoning and retrieval. When documents are supplied to large language models, selected metadata fields are included to enhance understanding. Examples of metadata include:- Authors
- Custodians
- Reviewer‑applied tags
- Entity attributes
Temporal modeling
The Knowledge Layer supports temporal accuracy when people or organizations change over time. Key behaviors include:- Capturing start and end dates for roles or titles when available
- Consolidating information into a single profile when dates cannot be determined
- Modeling employment and affiliation as person‑organization pairs
- Creating separate entries when a person changes organizations or when distinct employment periods are identified
How knowledge is stored
Extracted knowledge is stored across multiple database types to support different access patterns:- Relational database. Stores entities, relationships, and metadata.
- Text search database. Indexes textual topics and summaries.
- Vector database. Stores vectorized representations (embeddings) for advanced search and clustering.