All output tables include embeddings written directly to your configured vector store for efficient downstream retrieval.
Shared fields
All tables have two identifier fields for global uniqueness and human readability:Communities
This table contains the final communities generated by the Leiden algorithm. Communities are strictly hierarchical, subdividing into children as cluster affinity is narrowed.Example communities.parquet
Example communities.parquet
Community reports
This table contains the summarized reports for each community, generated by the LLM.Example community_reports.parquet
Example community_reports.parquet
Covariates
This optional table is generated when claim extraction is enabled. Claims typically identify malicious behavior such as fraud, so they are not useful for all datasets.Example covariates.parquet
Example covariates.parquet
Documents
This table contains the list of document content after import.Example documents.parquet
Example documents.parquet
Entities
This table contains all entities found in the data by the LLM.Example entities.parquet
Example entities.parquet
Relationships
This table contains all entity-to-entity relationships found in the data by the LLM. This is also the edge list for the graph.Example relationships.parquet
Example relationships.parquet
Text units
This table contains all text chunks parsed from the input documents.Example text_units.parquet
Example text_units.parquet
Working with Parquet files
Storage locations
By default, Parquet files are written to theoutput directory specified in your configuration:
settings.yaml
- Local filesystem
- Azure Blob Storage
- Custom storage
output/entities.parquetoutput/relationships.parquetoutput/communities.parquet- etc.
Next steps
Custom graphs
Learn how to bring your own existing graph data
Querying
Use the output tables for GraphRAG queries
Configuration
Configure storage providers and output settings