Our Media API offers the following functionalities:
Article analysis: We perform detailed analysis of the text of the article, returning
Entities (see here): Important expressions, both named (e.g., organizations, cities) and unnamed (e.g., dates).
Derived Entities are entities not explicitly mentioned in the text, but they can be derived with the help of our knowledge base (see below). For example, we can return countries and regions for locations (returning
Germanywhen the article mentions Berlin), industries for organization (returning
automotivefor Toyota), etc.
Semantic tags: Semantic tags are entities, keywords or concepts relevant for the article. We rank and standardize them based on their purpose. For a non-technical overview, see this page and this case study.
Sentiment (see here): We perform sentiment analysis for the whole article, individual sentences and entities.
Recommendation of related content: based on the content of the article, we recommend
Relevant photos (see here) from multiple photobanks, including our partners’ photos, big and small third-party photobanks, public photos from Wikipedia, etc.
Related articles – articles about similar topics (not supported yet)
Knowledge base (see here): All the returned tags and entities are linked to the Geneea Knowledge Base (GKB, Geneea KB). GKB combines existing open data (wikidata, DBpedia, OpenStreetMap, company registries, etc.) with our own private resources. GKB also supports custom properties (e.g. your internal ids) and items.
Localized Entities and Tags (see here): all entities and tags in analysis and recommendations can be presented in a language of your choice.
Feedback (see here): The quality and preferences can be automatically tuned based on the feedback for the user.
Integration: Typically our API is called from the publisher’s CMS. The journalists review the suggested tags. The API can be also used in a completely automated pipeline without any supervision.
Customization: Typically, the Media models are thoroughly customized (entity ids and labels, number of tags, preference of certain types of tags, creation of new tags, etc.)
The new API does not support the following features of the current V1 API. We will add them soon: