> Documentation index for agents: https://docs.rocketride.ai/llms.txt

# dictionary

A RocketRide text-processing node that asks a connected LLM to turn text or table content into a glossary of company-specific terms. Choose it when downstream users or agents need concise definitions of internal vocabulary rather than a general structured-data extraction.

## What it does

The node accepts text or table content and sends each incoming chunk to its required LLM connection with a structured prompt (`expectJson: true`) and instructions to return a single JSON array of definitions. It writes one document for every returned definition; each document contains the JSON-serialized definition and is marked as non-table content. Use it instead of `extract_data` when the output should be a reusable vocabulary of terms and descriptions, not rows with a predefined schema.

## Connections

| Connection | Required | Description |
| --- | --- | --- |
| `llm` | yes | LLM used to extract and define terms. |

## Lanes

| Lane in | Lane out | Description |
| --- | --- | --- |
| `text` | `documents` | Emits one definition document for every item returned by the LLM. |

## Configuration

This node has no local configuration fields. Connect an LLM and supply text on its `text` lane; the same extraction path is also used when the runtime provides table content.

## Notes

### Definition output

The built-in prompt asks the LLM to include company-specific language, acronyms, and terms whose in-company meaning differs from common usage — including terms that are ambiguous. It always requests one JSON array: if the LLM response is valid JSON but is not an array, the node raises a descriptive `ValueError` before emitting any documents, and invalid JSON continues to surface the response parsing error. The example shape used by the prompt is `{\"term\": \"...\", \"description\": \"...\"}`, but the node serializes each returned object without imposing additional fields.

### Dependencies

The node has no Python package requirements of its own: it relies entirely on the separately installed AI module.

### Chunk metadata

The node resets its output `chunkId` for every input object, then increments it for each emitted definition. It writes `isTable: false` and `tableId: 0` even when the input arrived through the table-processing path, so downstream nodes receive glossary entries as ordinary documents.

<!-- ROCKETRIDE:GENERATED:PARAMS START -->
<!-- Generated by nodes:docs-generate. Do not edit by hand. -->

## Schema

_No configuration fields._

## Source

[<svg viewBox="0 0 16 16" width="15" height="15" fill="currentColor" aria-hidden="true" style="vertical-align:-0.15em;margin-right:0.35em"><path d="M8 0C3.58 0 0 3.58 0 8c0 3.54 2.29 6.53 5.47 7.59.4.07.55-.17.55-.38 0-.19-.01-.82-.01-1.49-2.01.37-2.53-.49-2.69-.94-.09-.23-.48-.94-.82-1.13-.28-.15-.68-.52-.01-.53.63-.01 1.08.58 1.23.82.72 1.21 1.87.87 2.33.66.07-.52.28-.87.51-1.07-1.78-.2-3.64-.89-3.64-3.95 0-.87.31-1.59.82-2.15-.08-.2-.36-1.02.08-2.12 0 0 .67-.21 2.2.82.64-.18 1.32-.27 2-.27.68 0 1.36.09 2 .27 1.53-1.04 2.2-.82 2.2-.82.44 1.1.16 1.92.08 2.12.51.56.82 1.27.82 2.15 0 3.07-1.87 3.75-3.65 3.95.29.25.54.73.54 1.48 0 1.07-.01 1.93-.01 2.2 0 .21.15.46.55.38A8.013 8.013 0 0016 8c0-4.42-3.58-8-8-8z"/></svg> View source](https://github.com/rocketride-org/rocketride-server/tree/develop/nodes/src/nodes/dictionary)
<!-- ROCKETRIDE:GENERATED:PARAMS END -->
