search

foodkg / foodkg.github.io

Apache License 2.0
83 stars 42 forks source link

USDA_SPARQL_QUERY in app_kbqa returning no results #16

Open jks17 opened 3 years ago

jks17 commented 3 years ago

Hi,

I have successfully uploaded the USDA data, the ontologies and the three .Trig files to a Blazegraph instance and the example queries on this page: https://foodkg.github.io/whattomake.html work.

However, the fetch tag query in app_kbqa/data_builder/src/recipe.py and the USDA_SPARQL_QUERY in app_kbqa/data_builder/src/config/data_config.py both return no results. My url_endpoint is correct as the other queries are working. I am also able to explore both the USDA data and the Recipe data on the Blazegraph tool.

Kind Regards, Josh

dinani65 commented 2 years ago

I have the same problem. @jks17 did u fix it? if so, how?

Limtle commented 2 years ago

Hi, @dinani65 did you process the ontofox on foodon.txt successfully (in the recipe-handler folder)?

jks17 commented 2 years ago

I have the same problem. @jks17 did u fix it? if so, how?

hey @dinani65 - sorry for the late reply. I did not get it to work entirely (queries still don't work in blazegraph). However, the generated usda-pairs.csv in recipe-handler does provide a link between USDA info and ingredients in recipe1m so I used this for my use case

riaz commented 1 year ago

@jks17 were you still able to build the app_kbqa , I got everything u mentioned working.

jks17 commented 1 year ago

@riaz I did get most of it working in the end. There still wasn't an easy way for me to compare USDA info with ingredients. Did you follow the code exactly or did you change something?

anujatayal commented 1 year ago

I am also facing the same issue. usda_subgraphs.json and usda_entities.json are empty files. Any solution?

kokoro-ele commented 1 year ago

Hi, I followed every step and succussfully import the 3 TriG files and the query in app_kbqa/data_builder/config/data_config.py returns a empty set. Did anyone fix this?

saranshkg commented 9 months ago

Hello. I am facing this issue as well - exactly as described by @jks17. Has anyone been able to find a workaround or a solution to this issue? Kindly help.