I think this is a very big problem for the prioritization of information. And the source of multiple hallucinations
Welcome @Jackno1980_matadi
That’s how it generally is supposed to be according to my understanding.
You can use the system directive to pass instructions and date-time every time you make the API call.
2 Likes
Welcome to the forums!
Remember that when using the Gemini API that Gemini is a language model. Not a source of truth or information. Gemini and other LLMs are pattern systems that are specifically designed to handle and continue patterns.
They do not “know” anything. Anything that comes back is because it works its way into the pattern.
As @sps has said - if you want it to “know” something (ie - to include it as part of the pattern and increase its chance to reply), then you can include it as part of the system instructions or prompt. This is a common pattern for prompt engineering.
2 Likes
An API model shouldn’t know its own name, and it’s kind of annoying that the alignment does have the AI answering as being Bard or Gemini (depending on how the wind blows). That is the domain of the implementer.
What do you mean by “concept of time”? Is that in reference to problem-solving, or just knowing if it is the following day when you re-engage with a chat?
For time-critical applications, like a chatbot that schedules appointments, you can place the current and chat start time into the system message, and then also augment past messages with their sent times for the highest level of contextual understanding.
1 Like