Unexpected reference tokens appearing in assistant output

[_j]

They are citation references. However they are being written wrong. Where the AI needed to have written a (recycle/refresh) unicode code point to finish the single citation, the AI instead produced a repeat of the (outline star) unicode code point.

@_j

The “ugly things” are the AI writing its internal citations container, and looping with more file chunk references (that is invalid) with the wrong Unicode instead of closing them with the correct UTF-8 character that is prompted. The same symptom has been observed before.

@_j

This is an unlikely prediction, as it is not going to be trained and will have little meaning. That is likely why the AI will not close a citation, but instead outputs the middle character again, then a pattern of writing another citation index.

@_j

They are meaningless Unicode private-use code points, and OpenAI is attempting to use them with a semantically-based language model. The AI apparently has to get really desperate to have nothing else to write before getting out of a container with the instructed U+E201 code point, instead of repeating what it just wrote.

You are a consumer of OpenAI’s poor vector store product, internal prompt language, and choice of characters the AI won’t produce reliably, and using AI that won’t believe that you have the rights to tell it how to use tools in a “developer” message to improve the situation.