diffgram VS dataqa

As a few examples of how much depth we have considered, here's a detailed comparison with sagemaker. Part of an integration with scale. Part of code for labelbox integration, datasaur (scroll to trusted by for our logo) etc. To the best of my knowledge I am trying to track every firm that is in this direct space.

(Direct repo link https://github.com/diffgram/diffgram)

We list some benefits here but if I had to pick one thing, it's that it's a complete system. You can be up and running in 2 minutes on docker. And scale to "big tech co" level on multiple k8s clusters.

Hey, I am the creator and (only contributor today) of open-source https://github.com/dataqa/dataqa, a Python library to explore and annotate documents. It uses weak supervision, is based on spacy, and has a lot of opportunities to add more deep learning and ML functionality. I can guide you through it :-). This would be a great opportunity to be first and lead contributor of an open-source library (outside the creator).

I recently added a new feature to DataQA (https://github.com/dataqa/dataqa) to be able to extract entities from Wikipedia. All you need to do is upload a file with Wikipedia urls:

The open-source project is here: https://github.com/dataqa/dataqa. I have just released a feature which I have been working on for a while to solve a problem which I've seen a lot in industry: how to map entities found in text to large knowledge base ontologies.

The tool I developed and used for this problem: https://github.com/dataqa/dataqa

I have seen first hand at small and large companies how problems have been tackled with ML without trying a simple rule or heuristic first. And then, further down the line, the system has been compared to a few business rules put together, to find that the difference in performance did not explain the deployment of an ML system in the first place.

It's true that if your rules grow in complexity, this might make it harder to maintain, but the good thing about rules is that they tend to be fully explainable, and they can be encoded by domain experts. So the maintenance of such a system does not need to be done exclusively by an ML engineer anymore.

Here is where I insert my plug: I have developed a tool to create rules to solve NLP problems: https://github.com/dataqa/dataqa

After working in ML for more than a decade, I became frustrated over time with the lack of tools to create baselines using simple rules and heuristics. It is well known that most business problems out there can achieve decent baselines using only heuristics. This is why I have developed DataQA (https://github.com/dataqa/dataqa), which uses NLP rules to do common NLP annotation tasks, such as multiclass classification or named entity recognition.