how Knowledge Graphs could be used to provide context
📚 Definition number 0️⃣0️⃣0️⃣0️⃣0️⃣1️⃣0️⃣1️⃣
🌊 It is pretty easy to see how context is making really big waves recently. Not long time ago, there were announcements about Model Context Protocol (MCP). There is even saying that Prompt Engineers changed their job titles to Context Engineers. 😅
🔔 In my recent few posts about definitions I tried to show how Knowledge Graphs could be used to provide context as they are built with two types of real definitions expressed in a formalised language. Next, I explained how objective and linguistic nominal definitions in Natural Language can be linked to the models of external things encoded in the formal way to increase human-machine semantic interoperability.
🔄 Quick recap: in KGs objective definitions define objects external to the language and linguistic definitions relate words to other expressions of that language. This is regardless of the nature of the language under consideration - formalised or natural. Objective definitions are real definitions when they uniquely specify certain objects via their characteristics - this is also regardless of the language nature. Not all objective definitions are real definitions and none of linguistic definitions are real definitions.
💡 Classical objective definitions are an example of clear definitions. Another type of real definitions that could be encountered either in formalised or Natural Language are contextual definitions. An example of such definition is ‘Logarithm of a number A with base B is such a number C that B to the power of C is equal to A’. Obviously this familiar mathematical definition could be expressed in formalised language as well. This makes Knowledge Graphs capable of providing context via contextual definitions apart from other types of definitions covered so far.
🤷🏼♂️ At the same time another question appears. How is it possible to keep track of all those different types of definitions and always be able to know which one is which for a given modelled object? In my previous posts, I have shown how definitions could be linked via ‘rdfs:comment’ and ‘skos:definition’. However, that is still pretty generic. It is still possible to extend base vocabulary provided by SKOS and add custom properties for this purpose. Quick reminder: property in KG corresponds to relation between two other objects. Properties allowing to add multiple types of definitions in Natural Language can be created as instances of owl:AnnotationProperty as follows:
namespace:contextualDefiniton a owl:AnnotationProperty .
After that this new annotation property instance could be used in the same way as more generic linking definitions to objects in KGs. 🤓
🏄♂️ The above shows that getting context right way can be tricky endeavour indeed. In my next posts, I will try to describe some other types of definitions, so they can also be added to KGs. If you'd like to level up your KG in this way, please stay tuned. 🎸😎🤙🏻
#ai #knowledgegraphs #definitions
how Knowledge Graphs could be used to provide context
