I saw the same behavior in what was probably an early leak of the json model on the completions endpoint the very first time I try interacting with it.
You might consider writing the specification of json desired as an actual json schema, which includes both data types that are permitted, and also can include “example” keys to separate demonstration from misinterpretation.