We've shown that structured output wins for coherent extraction and orchestration wins for deep analysis. The question was whether you could use both in the same definition. You can now.
In our previous post, structured output beat ObjectWeaver on knowledge graph extraction. We promised a follow-up testing where orchestration actually shines. Here are the results.
We ran an honest experiment comparing ObjectWeaver against the Gemini Structured Output API for knowledge graph extraction from interview transcripts. The structured API won. This post explains why — and where orchestration actually earns its keep.
Reliably generating structured JSON from Large Language Models presents a fundamental challenge with two distinct solutions: grammar-constrained generation and LLM orchestration. Grammar-constrained generation (Outlines, Guidance, llama.cpp GBNF, Formatron) forces compliance through inference-time token masking—optimized for simple, flat schemas. ObjectWeaver orchestrates field-level generation with parallel processing, dependency management, and intelligent model routing—designed for complex production schemas where different fields demand different capabilities.
We chose the GNU Affero General Public License v3 (AGPL-3) for ObjectWeaver. This wasn't a decision we made lightly. In the world of open-source infrastructure, the choice usually falls between permissive licenses (MIT, Apache 2.0) and copyleft licenses (GPL, AGPL).
We chose AGPL-3 to ensure ObjectWeaver remains a community-driven standard while building a sustainable business. Here is why.