Are Large Language Models Suitable for Graph Computation? Progress and Prospects

· Source: cs.CL updates on arXiv.org · Field: Technology & Digital — Artificial Intelligence & Machine Learning, Data Science & Analytics, Mathematics & Computational Sciences · Depth: Advanced, extended

Summary

This paper provides a comprehensive review of Large Language Models (LLMs) for graph computation, addressing a gap in existing surveys that primarily focus on graph learning or text-attributed graphs. It introduces a role-based taxonomy, categorizing LLM applications into two paradigms: LLMs as executors, which directly solve graph tasks from descriptions, and LLMs as planners, which orchestrate problem formulation, reasoning decomposition, and external tool invocation. The review indicates that LLMs show promise for simple, small-scale graph tasks, performing reasonably well on graphs up to 50 nodes. However, they remain unreliable for large-scale and exactness-demanding computations due to issues like hallucination and performance degradation with increased graph size or reasoning depth. The authors also summarize available datasets and propose four future research directions.

Key takeaway

For AI Engineers evaluating LLM integration into graph analysis pipelines, recognize that direct LLM execution is suitable only for small, simple graphs where exactness is not critical. For large-scale or correctness-demanding graph computation, you should prioritize planner-based approaches. Implement LLMs to orchestrate external tools, generate code, or manage multi-agent systems, leveraging their reasoning for task decomposition while delegating precise algorithmic execution to specialized graph libraries. This strategy mitigates hallucination and scalability issues inherent in direct LLM execution.

Key insights

LLMs excel as graph computation planners but struggle as direct executors for large, exact tasks.

Principles

Method

A role-based taxonomy categorizes LLMs in graph computation: "executors" (direct solving via prompting, encoding, post-training) and "planners" (orchestrating external tools via code, functions, multi-agents).

In practice

Topics

Best for: Research Scientist, AI Scientist, Machine Learning Engineer, AI Engineer

Related on AIssential

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by cs.CL updates on arXiv.org.