-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Breaking question down into individual parts #290
Comments
Hi @ChakshuGautam, I am interested in working on this issue. Before asking to assign it to me, I would require some clarifications from my end :
|
@AbhishekRP2002 updated the description. You can start working on this with a draft PR. We can work on this collaboratively. |
Sure , I'll share a draft this weekend. Any medium other than Discord where we can connect and discuss? |
I'll be available on Discord. We can schedule a call from there if needed. |
https://allenai.github.io/Break/ |
hi @ChakshuGautam , I was looking forward to contribute here. Since, it's also been inactive since long. Having some doubts.
can I get sample queries/questions. With knowledge base (if it exists) to start the work ? |
Microsoft ToolTalk is a relevant benchmark for assessing the ability of LLMs to call multiple tool APIs sequentially, which is sort of a superset of this problem statement. Paper link - https://arxiv.org/pdf/2311.10775.pdf I would like to say that, in my personal experience in trying to develop a sequential tool-calling LLM which involved trying to break down queries, most open-source LLMs failed to produce good results as of November 2023. A simple one-shot prompt via GPT-4 as well as a prompting pipeline with GPT3.5 produced satisfactory results. Feel free to involve me in this if possible. The paper also has a comprehensive list of various benchmarks that could be useful while selecting an appropriate benchmark for this issue - |
Approaches to try out
References
The text was updated successfully, but these errors were encountered: