Semantic Grid
One Prompt, N Independent Runs
Ask a chat to compare six vendors on three attributes and you get eighteen facts flattened into prose — one silently missing, none traceable, and rechecking a single one costs a full regeneration. Semantic Grid makes the prompt a column definition: authored once, fanned out across rows as independent runs, each cell carrying its own source and re-runnable on its own. Where Parallel Alternatives is N variants of one task, this is one task over N subjects.
Framing
The problem
Comparing many things across many attributes collapses into prose where no fact can be traced, counted, or rechecked on its own.
The pattern
Make the prompt a column definition, fan it out across the rows as independent runs, and give every cell its own source and its own retry.
Why chat breaks here
A transcript holds one answer per turn, so eighteen facts arrive as a single blob and rechecking any one of them costs a full regeneration of the other seventeen.
Risks
A grid of confident-looking cells invites reading it as a dataset — without per-cell provenance and a visible low-confidence count it industrialises unverified claims.
Avoid when
The question has one subject: a single deep answer beats a one-row table wearing a schema.
DOPE evaluation
- Directability
- Edit a column prompt and only that column re-runs; add a row and only its cells fill — the unit of work is the cell, not the table
- Observability
- Every cell carries its own source chip and confidence dot, and the counter states the run exactly — 18 cells · 3 low-confidence · 1 re-run · 4,210 tokens
- Predictability
- The schema is declared before anything runs: N rows × M column prompts is N×M cells, each answering the same stated question
- Explainability
- Open any cell for the snippet that produced it, with its own tokens and latency — provenance is per answer, not per document
In the wild
- Elicit
- Clay
- Airtable AI Fields
FAQ
When should I avoid the Semantic Grid pattern?
The question has one subject: a single deep answer beats a one-row table wearing a schema.
What problem does Semantic Grid solve?
Comparing many things across many attributes collapses into prose where no fact can be traced, counted, or rechecked on its own.
Why is chat the wrong fit for this?
A transcript holds one answer per turn, so eighteen facts arrive as a single blob and rechecking any one of them costs a full regeneration of the other seventeen.