Structured Extraction
FlagshipTurn a messy customer message into strict JSON without inventing a value you weren't given.
6 hidden cases, live model
Your prompt
Attempt 1, 0 of 4,000 charactersWrite a prompt before running. The editor is empty.
Ready when you are
Write a prompt, then send it into the arena.
A pace to beat appears after your first completed run.
The arena
6 hidden casesWaiting for a promptNo runs yet. Write a prompt and press Run tests.
- Hidden case
- Hidden case
- Hidden case
- Hidden case
- Hidden case
- Hidden case
Expand a tile for the check that decided it and the model response. Withheld text never leaks the hidden message.
Attempt history
The first run puts a bar here.
Mission
output disciplineConvert each incoming customer message into strict JSON with exactly four fields: order_id, reason, amount_usd and wants_replacement. If a value isn't present in the message, mark it unknown rather than guessing it.
- C1 Output always parses as valid JSON
- C2 Exactly the four required fields, correct types
- C3 Missing values marked unknown, never invented
- C4 Amounts preserved exactly, as numbers
- C5 Ambiguous references handled without fabrication
- C6 Two requests in one message both captured
What a strong prompt does here
A strong prompt defines the output shape, names the exact field names, and covers the part most people miss: what to do when a value is missing or when two numbers compete. It doesn't get longer than it needs to be; it covers the cases you can't see.
rule checkedjudged
Take it with you
No hidden inputsRun once to export a report.