Elephant AI integrates with the Responses API to provide artificial intelligence to and from all Elephant modules.
Site administrators can decide which group of users is able to use the chat with the AI models. Once in the chat, the user will be able to ask questions, and receive answers in natural language, using the same language he uses to ask the questions.
Questions can be related to the information provided or to Elephant modules data. For example, Which projects use JakartaEE?, Which partners offer this service?, What's the purpose of this site?, and so on.
Elephant AI also allows calling the AI models with operation-oriented instructions, to provide a more generic answer in natural language or a specific format.
API Key and a Prompt ID.Storage IDs and/or File IDs.Personalities, to provide different behaviors (currently CHAT and CREATOR).Personalities based on user's role.Developer and System instructions to ensure a correct behavior and compatibility with user language.Tools from all modules to instruct responses with real data.On-site chat with the AI models.natural language, or in a specific format.files accessible to the models.vector DBs (automatic using AI Contexts).Length of Knowledge aims to provide different content (answers) to different kind of users, mainly based on user's role, but also user self identity. This model also has a big impact on token expenses.
Elephant adds new context functionality related to the Elephant AI project.
Storage ID set for the CHAT personality.When editing a context, you can select it as a feed for the AI models. It's important to keep in mind that the Vector DBs will be fed with the HTML content transformed to Markdown.
Keep the content easy to understand for your intended target. Create captions to clarify different sections. You can upload images for the web, but only the text will be used to feed the AI models. Use bold for important parts of the text, or italic, or monospaced.
As it happens with specific Markdown content for the AI models, it's important to follow the best practices. The AI models will cross-reference the information you provide, unless instructed not to (but what's the fun then?). You should review the nomenclature to allow good cross-references.
An example of Elephant Wiki using best practices:
In some context
---++Projects The projects ...
In another context
See **Projects** to ...
Elephant AI can be configured to respond to live-data. This is the list of properties, some associated to an AI Personality:
| Property | Description |
|---|---|
| AI.OpenAI.APIKEY | The API Key you get from OpenAI platform. |
| AI.OpenAI.PromptID | The Prompt's ID. You need a project to get the ID. |
| AI.Run.Help | If set, it's an address to your own description of what the AI provides. |
| AI.Run.Debug | Adds information about the steps the AI is using. |
AI.Personality.Model |
The model used by the AI Personality. Defaults to gpt-5-mini. |
AI.Personality.VectorStoreIDs |
Storage ID where your selected content will be uploaded. |
AI.Personality.FileIDs |
File Ids to use by this AI Personality. Unless necessary, use Vector Stores instead. |
AI.Personality.AccessRole |
The role required to interact with the AI Personality. |
AI.Personality.IconButton |
If true, shows a fixed position icon. |
AI.Personality.DossierRoots |
Category IDs of the projects will be sent to the AI Personality. |
AI.Personality.ContactsRole |
Contacts with the given roles will be sent to the AI Personality. |
AI.Personality.UserDocs |
User documentation will be sent to the AI Personality. |
This is a brief description of current personalities and how they are used:
CHAT |
The main personality, the one you'll be using first. The Ask AI chat uses this configuration. The features of this personality are:
|
CREATOR |
The CREATOR personality aims to generate content. The main goal is to be attached to content editors. Whether is available to admins and/or users is controlled by the AccesRole, same as for CHAT.
|