How Is Kumo Relational Different from an LLM or Text-to-SQL?
How Is Kumo Relational Different from an LLM or Text-to-SQL?
Kumo Relational predicts unknown or future outcomes from structured relational data. A large language model (LLM) generates or interprets language, while text-to-SQL translates a natural-language question into a database query that retrieves existing records.
These capabilities complement one another rather than solving the same problem.
Compare the workloads
Why the relational graph matters
Flattening several tables into text or serializing them as JSON does not preserve database structure efficiently. Kumo Relational uses table metadata, primary-foreign key relationships, timestamps, and sampled neighborhoods to reason over the relational graph.
Its prediction objective is also different from next-token generation. Kumo Relational is designed for classification, regression, forecasting, and link prediction tasks expressed in PQL. See Prediction Types.
Use Kumo Relational with an LLM
An application can use each component for what it does best:
- An LLM interprets the user’s request or manages the conversation.
- Application logic formulates or selects an approved PQL query.
- Kumo Relational returns the prediction.
- The LLM explains or presents the result in natural language.
Keep prediction execution and language generation distinct so the application can validate the PQL task and preserve the returned values. For architectural background, see Kumo Relational: A Relational Foundation Model.