Log in
Log into community
Find answers from the community
View all posts
Related posts
Did this answer your question?
π
π
π
Powered by
Hall
Inactive
Updated 3 months ago
0
Follow
When using the SubQuestionQueryEngine I
When using the SubQuestionQueryEngine I
Inactive
0
Follow
M
Milkman
last year
Β·
When using the SubQuestionQueryEngine, I keep running into the issue of 'KeyError: 'comparison'. I have multiple documents as query engine tool and feed them in the query_engine_tools parameter in constructing the SubQuestionQueryENgine.
L
M
14 comments
Share
Open in Discord
L
Logan M
last year
seems like it's hallucinating the name of an index/query_engine_tool ?
What kinds of names did you use?
M
Milkman
last year
I just use the file name as teh tool name.
L
Logan M
last year
are the names super similar or confusing?
M
Milkman
last year
I'd say they are similar but not confusing
L
Logan M
last year
can you share them? Just wondering why it's hallucinating a name. Usually it helps to re-engineer the names, at least in my experience
M
Milkman
last year
XXX AUM May 2023.pdf, XXX AUM April 2023.pdf
L
Logan M
last year
huh, well, I guess the LLM is just being silly then haha
I feeeeeell like I encountered this last week, and then we changed the prompt to better avoid this. What llama-index version are you on?
M
Milkman
last year
I'm actually quite far behin on 0.6.30
M
Milkman
last year
Oh that's why sometimes it works sometimes it doesn't
L
Logan M
last year
oh wow, that is quite far behind π Updating may... be a little painful lol
L
Logan M
last year
I can't even remember what's changed since then
L
Logan M
last year
feels like 0.6.30 was a lifetime ago
M
Milkman
last year
Yea sadly we haven't got the Azure Function calling API, so I was reluctant to change
L
Logan M
last year
ah, that makes sense
Add a reply
Sign up and join the conversation on Discord
Join on Discord