Fetching from the wire…
01
02
03
04
05
06
07
08
Infra2026-06-12 · source-backed
AWS detailed a feature where you supply 3-10 example documents with expected outputs and the system refines the extraction blueprint automatically. It targets the brittle prompt-engineering step in document IDP pipelines. If you're doing structured extraction at scale on AWS, this turns hand-tuning into example-driven tuning, which is the right direction.
Each link below shares sources, entities, or timing with this story.
AWS uses Neptune / Shared entity: AWS / Same source domain / Shared topic / What happened next
Linked by a graph relationship (AWS uses Neptune); both cover AWS; reported by the same outlet (aws.amazon.com).
OpenAI partners with AWS / Shared entity: AWS / Same source domain / Earlier coverage / Tension
Linked by a graph relationship (OpenAI partners with AWS); both cover AWS; reported by the same outlet (aws.amazon.com).
OpenAI partners with AWS / Shared entity: AWS / Same source domain / What happened next
Linked by a graph relationship (OpenAI partners with AWS); both cover AWS; reported by the same outlet (aws.amazon.com).
Linked by a graph relationship (OpenAI partners with AWS); both cover AWS; reported by the same outlet (aws.amazon.com).
Bedrock built by AWS / Shared entity: AWS / Same source domain / What happened next
Linked by a graph relationship (Bedrock built by AWS); both cover AWS; reported by the same outlet (aws.amazon.com).
Linked by a graph relationship (Bedrock built by AWS); both cover AWS; reported by the same outlet (aws.amazon.com).
OpenAI partners with AWS / Shared entity: AWS / What happened next / Tension
Linked by a graph relationship (OpenAI partners with AWS); both cover AWS; picks up the AWS thread on 2026-08-13.
Linked by a graph relationship (OpenAI partners with AWS); both cover AWS; picks up the AWS thread on 2026-06-27.