Your GraphRAG system verbalizes every retrieved triple...

The primary issue is the linear growth of token usage relative to the number of triples. Simply increasing the context window is a temporary fix that does not address the underlying growth rate. By switching to embedding fusion, you can maintain a fixed token cost regardless of the subgraph size, or alternatively, refine the upstream pruning logic to ensure only the most relevant triples consume the budget.