Skip to content
KNIME Documentation
Main Navigation Get startedBuildWork with KnimeAccount and adminRelease notesDeveloper tools
Community Hub
DevelopersKnime
Sidebar Navigation

Getting Started

Installation

User Guide

Release Notes

Install Extensions

Building Workflows

Components

Flow Control

Expressions

File Handling

Deployment

Integrated Deployment

Workflow Invocation

Best Practices

Advanced Features

AI Extension

Get Started

Build an Agent

Inject context with RAG

LLM Providers

Tutorials

Summarize product reviews

Product FAQ assistant

Restaurant agent

Your first local agent

Task extractor

Reporting

Kerberos

Extensions

Database

Overview

Tutorials

Read and filter data from a database

Write a transformed dataset to a database

Concepts

Ports and Sessions

Query Generation

Type Mapping

Deprecated Framework

Connecting

Connect: Dedicated Node

Connect: File-Based Database

Connect: Generic DB Connector

Register a JDBC Driver

Install Third-Party Driver Plug-in

Drivers on Hub and Server

Kerberos Constrained Delegation

Reading and Transforming

Read Data

Transform Data Visually

Run a Custom SQL Query

Parameterize a Query

Writing and Modifying

Insert, Update, or Merge

Delete Rows

Bulk Load Data

Create and Remove Tables

Use Transactions

Reference

Connector Node Settings

JDBC Driver Reference

Deprecated Node Mapping

Migrate Deprecated Workflows

Python

Overview

Tutorials

Python Scripting Quickstart

Data App Development Using Plotly

Data Processing

K-AI Scripting Assistant

Data Type Conversion

Batch Processing

Jupyter Integration

Environment Management

Pixi Configuration

Dependency Management

Environment Persistence

Channel Mirrors & Air-Gapped Setups

Conda Migration

Alternative Configurations

Conda and Miniforge Setup

Conda Environment Propagation

Manual Python Configuration

Legacy Node Migration

Concepts

Pixi Backend Architecture

Storage Logic

Python Environments on Executors

Reference

Python Scripting API

Bundled Packages

Executor and Hub Configuration

Troubleshooting Guide

API Reference

Inputs and outputs

Classes

Views

Utility functions

R

Deep Learning

Snowflake

Google Cloud

Azure

AWS

Big Data

Big Data Admin

Big Data Secured Cluster

Databricks

Microsoft Fabric

Power BI

Tableau

Report Designer

H2O

Changelogs

Version 5.12

Version 5.11

Version 5.10

Version 5.9

Version 5.8

Version 5.7

Version 5.6

Version 5.5

Version 5.3

Extensions

Prompt with structured output ​

Instruct a language model to return structured data directly in table columns instead of free-form text.

When this is useful ​

Structured output is useful when model responses need to be parsed, validated, or processed automatically into KNIME workflows.

Use structured output when you want to:

  • Extract structured information from text into predefined columns
  • Define the exact output schema the model should follow
  • Reliably integrate LLM output into automated or rule-based workflows
  • Extract one or multiple items from each input row

If you only need free-form text output, use a simple prompt instead.

Build a prompt with structured output ​

Prerequisites

Before you start, make sure that you have:

  • installed the KNIME AI Extension (see Install the KNIME AI Extension).
  • configured credentials for a supported provider (see LLM Providers).

To prompt a model for structured output, follow these steps:

  1. Configure the LLM Prompter output format
  2. Define the output structure
  3. Configure output columns

1. Configure the LLM Prompter output format ​

Use the LLM Prompter node and configure it as follows:

  • Provide the input text column containing the prompt
  • Set Output format to Structured

This makes structured output configuration options available.

2. Define the output structure ​

In the Output Structure section, configure:

  • Target object name: A descriptive name for the items being extracted (e.g., "Actionable tasks", "Product features")
  • Target object description: Describe what should be extracted from the input text (e.g., "Tasks mentioned in the meeting that should be added to the board")
  • Target objects per input row: Determines how many items are extracted for each input row
    • Single: Extract exactly one item with the defined columns per input row
    • Multiple: Allow the model to extract one or more items with the defined structure per input row. The input columns will be duplicated for each extracted item.

3. Configure output columns ​

Define the columns that will contain the extracted data. For each column, specify:

  • Column name: The name of the output column
  • Data type: The data type (String, Integer, etc.)
  • Quantity: Whether the field is single-valued or can contain multiple values as a list
  • Description: Describe what this field should contain, including any constraints or allowed values

The model will return data structured according to these column definitions.

Example ​

See structured output in action with this complete example on KNIME Hub:

  • Extract multiple tasks from meeting notes

JSON

Some providers like OpenAI also support JSON as an output format. Check out this example on the Hub: Extract structured data from text.

Next steps ​

Follow this tutorial to learn how you can extract structured data with a local model using Ollama:

  • Extract tasks from meeting notes
Pager
Next pageInstallation