The advent of cloud-based large language model (LLM) services such as ChatGPT (Generative Pre-Trained Transformer) has given rise to a wide array of novel artificial intelligence (AI) applications. In particular, LLMs have been used to power AI assistants that serve as intermediaries between human users and online web services, namely, web-based application programming interfaces (web APIs). These AI assistants allow users to make requests in natural language to initiate complex processes, ranging from searching a database to making a reservation. We are exploring the development of AI assistants that can intelligently search for and process species occurrence data served by the Integrated Digitized Biocollections (iDigBio) Portal. Though the portal already provides a human-friendly search interface, it is tailored for a very particular use case: finding and inspecting records that match the user’s search parameters. However, the underlying iDigBio APIs that power the search interface offer direct access to biodiversity data and metadata that can support a wider range of applications. An LLM-powered AI assistant with access to such APIs has the potential to redefine how researchers discover and interact with scientific data by 1) allowing users to interact with scientific databases using natural language, 2) serving as a single unifying interface for many different use cases, and 3) enhancing the user’s experience with AI insights that are backed by citable, curated data. Fig. 1 demonstrates a prototype chatbot we have developed, which interfaces with the iDigBio Portal. The chatbot uses OpenAI’s GPT-4 to understand user requests and call the appropriate APIs as needed. It currently has access to the following iDigBio APIs: The Search API allows the chatbot to perform the same search functions as the portal search interface. The results of the search can be observed by either directly calling the API from the user's web browser, opening the existing portal search interface with generated search parameters, or visualizing the geographic distribution of matched records on an interactive map. The Download API allows the chatbot to package search results as a Darwin Core Archive to be delivered by email. The Summary API allows the chatbot to collect statistics across all of iDigBio’s data, such as a breakdown of record counts for unique species reported within a particular geographic region. The Search API allows the chatbot to perform the same search functions as the portal search interface. The results of the search can be observed by either directly calling the API from the user's web browser, opening the existing portal search interface with generated search parameters, or visualizing the geographic distribution of matched records on an interactive map. The Download API allows the chatbot to package search results as a Darwin Core Archive to be delivered by email. The Summary API allows the chatbot to collect statistics across all of iDigBio’s data, such as a breakdown of record counts for unique species reported within a particular geographic region. Because the chatbot is intended for use by researchers, transparency is critical. When responding to user requests, LLMs often include their own internalized knowledge—which may be unreliable but difficult to verify—or make up information entirely. Thus, it must be abundantly clear how the chatbot forms its responses, in particular how the LLM interprets user requests and how it queries external APIs, such that users may independently assess the correctness of the chatbot's actions and link its conclusions back to data. The approach we adopted for the design of our prototype is illustrated in Fig. 2; whenever the chatbot initiates a data retrieval or analysis process, a detailed log of that process is embedded in the conversation, including the sequence of actions taken and their inputs and outputs. The chatbot's behavior is tightly controlled by the rigid use of specialized AI agents with expert-defined validators (Fig. 3). Importantly, we do not allow the LLM to respond freely to user requests; rather, we use a fixed set of AI agents that are specialized to produce structured outputs that follow strict schema as enforced by the agent's assigned validator. An orchestrator agent is responsible for deciding which agent is most appropriate to handle each request. If no agent is chosen, the system does not attempt to answer the user's request. As a prototype, the functionality of the chatbot is currently limited to the few illustrative use cases we have outlined. However, as the system is incrementally refined and expanded, we envision the single chatbot interface to be of interest to both the general public and researchers alike. For the general public, it may be a useful tool to learn about biodiversity in their local community and around the world. Meanwhile, researchers may find the chatbot useful for quickly navigating and exploring iDigBio's hosted data and APIs. The prototype is hosted online at chat.acis.ufl.edu with source code in GitHub.
Read full abstract