Hi all I m playing around with

Hi all! I'm playing around with ComposableGraph and DecomposeQueryTransform but am facing some issues:

When locally running the example notebook here, after querying with Compare and contrast the airports in Seattle, Houston, and Toronto. the decomposed query never queries for Toronto
Using a custom reduced version of the above notebook, sometimes the answer for one of the elements in a comparison query is not synthesized even though the node from its corresponding document is retrieved correctly, as can be seen from calling response.get_formatted_sources. E.g.: Querying for Compare Boston's, Houston's and Seattle's population decomposes the query for each city but the synthesized answer says that Boston's population was not in the context, although one of the retrieved nodes contains the text ...and a population of 675,647 as of 2020...
Using the same custom notebook from 2, querying for Compare Boston's, and Houston's population returns the correct answer, whereas querying for Compare Houston's and Boston's population (flipping the cities names) can't find Boston's population. I haven't been able to reproduce this one again but it might be related to the previous point

Would really appreciate some guidance 🙏

2 comments

Have you tried using the sub-question query engine instead? I think it's a bit more stable/robust, the two components you are using are not completely maintained at the moment 😅

uunknown

@Logan M First of all, thank you so much for your help! It seems to work fine by following your suggestion and using SubQuestionQueryEngine and VectorStoreIndex.
I understand we can use SubQuestionQueryEngine to substitute DecomposeQueryTransform. But what about replacing ComposableGraph? Putting all documents in the same VectorStoreIndex might not be the best idea, I could write my own index to do that but then it would be the same as reimplementing ComposableGraph. Any thoughts?

Add a reply

Find answers from the community

Hi all I m playing around with