Artificial Intelligence/Generative AI: Difference between revisions
No edit summary |
|||
| (6 intermediate revisions by the same user not shown) | |||
| Line 9: | Line 9: | ||
=== Ensuring capitalization of prompt knowledge === | === Ensuring capitalization of prompt knowledge === | ||
* Listing useful prompts, and creating metrics for them | * [https://docs.google.com/spreadsheets/d/1Iq4_vJcPEuCNQa9wa5aX3sES_67q5MJZT9-3E3SX8g4/edit#gid=0 Listing useful prompts], and creating metrics for them | ||
| Line 25: | Line 25: | ||
* Document good practises | * Document good practises | ||
* Document things we could also implement | * Document things we could also implement | ||
* [[Experiments/GenAI]] | |||
=== Think hard about how we can use it === | === Think hard about how we can use it === | ||
* Data quality | ==== Data quality ==== | ||
* [[Artificial Intelligence/Data quality]] | |||
==== Data extraction ==== | |||
==== Content synthetisation ==== | |||
==== Data models generation ==== | |||
==== Code generation ==== | |||
==== Food intake analysis ==== | |||
==== Natural search parsing ==== | |||
* [[Artificial Intelligence/Search]] | |||
* https://www.elastic.co/search-labs/blog/large-language-models-elastic-code-langchain | |||
* those are some of the potential themes, but there are many others | |||
* https://www.elastic.co/fr/cloud/generative-ai | |||
* https://eliatra.com/blog/chatgpt-and-llms-to-enhance-opensearch-elasticsearch-usability/ | |||
* https://www.elastic.co/search-labs/blog/rag-with-llamaIndex-and-elasticsearch | |||
* https://www.reddit.com/r/elasticsearch/comments/114ckdf/use_natural_language_to_query_elasticsearch_by/ | |||
=== Don't be paralyzed by potential errors or phantasms === | === Don't be paralyzed by potential errors or phantasms === | ||
| Line 36: | Line 52: | ||
=== Prioritize and implement key projects === | === Prioritize and implement key projects === | ||
* [https://github.com/openfoodfacts/openfoodfacts-ai/issues/289 Leverage Generative AI across Open Food Facts (tracker) #289] | * [https://github.com/openfoodfacts/openfoodfacts-ai/issues/289 Leverage Generative AI across Open Food Facts (tracker) #289] | ||
[[Category:GenAI]] | |||
[[Category:Artificial Intelligence]] | |||
Latest revision as of 08:36, 28 August 2024
Creating a foundation service
- Creating a foundation wrapper that could execute GenAI requests, and abstract the model being used (using cloud services at first)
- Ensuring 3rd parties can't abuse the service, while community developpers can use it freely
- Making testing and iteration easy.
- Taking safety measures so that it doesn't cost the Open Food Facts NGO too much
Ensuring capitalization of prompt knowledge
- Listing useful prompts, and creating metrics for them
Avoiding wasteful compute
- Ensuring outputs are stored and shared
- Ensuring we group prompts
- Ensuring prompts are iterated and evaluated before being run at large scale
Enhancing how we work and volunteer
- Ensuring knowledge about Open Food Facts as an org is well disseminated so that LLMs can help us more efficiently (eg: that it knows what Robotoff is, or which database we're using, …)
- Looking for opportunities in the tools we already use (eg GitHub Copilot from GitHub, new LLM features in Odoo, …) and new tools that could save us time or increase our impact
Monitor and document innovative usages outside Open Food Facts
- Document good practises
- Document things we could also implement
- Experiments/GenAI
Think hard about how we can use it
Data quality
Data extraction
Content synthetisation
Data models generation
Code generation
Food intake analysis
Natural search parsing
- Artificial Intelligence/Search
- https://www.elastic.co/search-labs/blog/large-language-models-elastic-code-langchain
- those are some of the potential themes, but there are many others
- https://www.elastic.co/fr/cloud/generative-ai
- https://eliatra.com/blog/chatgpt-and-llms-to-enhance-opensearch-elasticsearch-usability/
- https://www.elastic.co/search-labs/blog/rag-with-llamaIndex-and-elasticsearch
- https://www.reddit.com/r/elasticsearch/comments/114ckdf/use_natural_language_to_query_elasticsearch_by/
Don't be paralyzed by potential errors or phantasms
- It is possible to mitigate/eliminate those potential errors by keeping humans in the loop, and adopting a copilot approach
- These new techniques can be hidden as a helper in the UI (like a magic button), with the proper warnings