Update README.md
Browse files
README.md
CHANGED
|
@@ -10,13 +10,16 @@ pretty_name: Agentic data access benchmark
|
|
| 10 |
|
| 11 |
# Agentic Data Access benchmark (ADA benchmark)
|
| 12 |
|
| 13 |
-
Agentic Data Access benchmark is a set of real-world questions over few closed
|
| 14 |
-
|
|
|
|
|
|
|
| 15 |
|
| 16 |
-
ADA benchmark was created because of severe short-comings found in closed-domain assistants in the wild.
|
| 17 |
-
|
| 18 |
-
to sufficient data and is unable to perform complex or sequential operations over that data.
|
|
|
|
| 19 |
|
| 20 |
-
##
|
| 21 |
|
| 22 |
-
|
|
|
|
| 10 |
|
| 11 |
# Agentic Data Access benchmark (ADA benchmark)
|
| 12 |
|
| 13 |
+
Agentic Data Access benchmark is a set of real-world questions over few "closed domains" which can benefit tremendously from AI assistants/agents.
|
| 14 |
+
Closed domains are domains where data is not available implicitly in the LLM as they reside in secure or private systems e.g. enterprise databases.
|
| 15 |
+
If you are evaluating an AI product or building your own assistant over closed domains, then you can use the nature of questions here to
|
| 16 |
+
qualitatively measure the capabilities of your assistants/agents.
|
| 17 |
|
| 18 |
+
ADA benchmark was created because of severe short-comings found in closed-domain assistants in the wild.
|
| 19 |
+
We found that apart from few basic canned questions or workflows, the assistants were struggling to do anything new.
|
| 20 |
+
This was found to be because the assistant is not connected to sufficient data and is unable to perform complex or sequential operations over that data.
|
| 21 |
+
We call the ability of an AI system to agentically use and operate on data as agentic data access.
|
| 22 |
|
| 23 |
+
## Learn more
|
| 24 |
|
| 25 |
+
Learn more about agentic data access and benchmark here: https://github.com/hasura/agentic-data-access-benchmark
|