robot_chain
Execute multiple ROBOT ontology commands as a pipeline, passing objects in memory for efficiency without writing intermediate files.
Instructions
Execute a chain of ROBOT commands in a single process.
Ontology objects pass in-memory between steps — much more efficient
than writing intermediate files. Only the first step typically needs
an input key and only the last step needs an output key.
Each step is a dict with:
command: the ROBOT command name (e.g. "merge", "reason")All other keys are command arguments. Use the long flag name without leading dashes, with hyphens replaced by underscores.
Argument mapping rules:
Underscores become hyphens:
ontology_iri→--ontology-irilistvalues repeat the flag:{"input": ["a.owl", "b.owl"]}→--input a.owl --input b.owlboolvalues become"true"/"false"stringsstr/intvalues become a single flag-value pair
Example steps::
[
{"command": "merge", "input": ["edit.owl", "base.owl"]},
{"command": "reason", "reasoner": "ELK"},
{"command": "annotate", "ontology_iri": "https://example.org/my.owl"},
{"command": "convert", "format": "ofn", "output": "result.owl"}
]Tip: to discover available flags for a command, pass "help": true
in a step, e.g. [{"command": "merge", "help": true}].
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| steps | Yes | ||
| working_directory | No | ||
| catalog | No | ||
| prefixes | No | ||
| add_prefix | No | ||
| noprefixes | No | ||
| verbose | No | ||
| strict | No | ||
| xml_entities | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||