Lifetime revenue: $0
Collaborator(s): Soheil Alavi
Stage: Prototype
Technologies: Scala for APIs and NLP, OpenLink Virtuoso (graph DB to store DBpedia), HTML, CSS, and jQuery for the frontend
In 2010, Semantic Web was all the rage. The idea that every company or organisation could standardise their data around an ontology and connect it up with every other organisation’s data into one giant graph that anyone could navigate was every computer scientist’s ultimate fantasy.
Tim Berners-Lee who invented the Web called it Web 2.0, and many thought it would become the foundation upon which the next Facebook or Google would be built, and so VC money was pouring into Semantic Web startups, and startups like Wavii, Qwiki, and Metaweb who later on got acquired by the likes of Google and Yahoo! were gaining a lot of traction.
Most of the web back then (and probably today, if you exclude Instagram and TikTok) was in textual form and could not be easily linked to the Semantic Web. My vision was to connect textual data like emails, news articles, and blog posts to the Semantic Web, allowing users to tap into a world of relevant information behind the documents they were reading, as well as to help expand the portion of the web that was semantic.
The idea was to use natural language processing (NLP) to identify and tag all the entities and topics mentioned in any text, and to then link them to their corresponding entities (via URIs) in the Semantic Web.
Our vision for AYLIEN was to become the layer between textual data and the Semantic Web.
We built 2 plugins both intended for end users:
The project fell apart after we hit a few roadblocks:
Despite all of this, we had built a compelling demo that showcased the potential of a mainstream application for the Semantic Web, and given how hot that space was back then, that demo helped us raise $500k in seed financing for AYLIEN and we were off to the races.