Reasoning Mechanism and Project Halo

After a long silence I am back again to unleash the ideas through this blog. A while ago I had a look at the Questions of Project Halo and that made me thinking as how can I represent chemical elements and work out a general mechanism to represent elements, compounds and chemical reactions.

What I found that using the classification described in Tree of Porphyry it was easy to describe them all and also that made the whole scenario simple to explain. Basically the chemical reactions has 3 core parts. Chemical Elements (including molecules), Compounds and the Chemical Reactions. For a chemical reaction to proceed we need to either elements or compounds or a mixture of both. The result is again a compound, element etc.

In the future posts I will discuss the procedure I am following to tackle the elementary level problems in chemistry. I would love to hear from the readers if they have a problem scenario in mind they want to discuss and then we can work out how to solve this using the reasoning mechanism I am working on. The more complex the problem is, the better it will be for me work out an appropriate way to solve the same.

Until Next Time....

Facts, Beliefs, Truths, Goals, Statements

Off-late I've been busy reading about Semantics of Facts and Goals etc. There are many things in our day-to-day life that we come across. These are Statements, Facts, Goals, Beliefs, Truths, Obligations etc. Most of what we know or don't know fall in any (or more) of these categories. This made me thinking as what is this all about? What is the common thing among all these? What differentiates them? and many more questions pertaining to this topic.

Recently while researching on these topics I could draw these relations.

1. Statement is the common ancestor of Goal, Beliefs, Obligations, Truths, Facts etc.
2. Except Goal everything works is valid for a given time (has time component) and place.
3. Expression of goal needs two states for the same object. One is the initial state and one is the State of the object at any given time t when we claim the object has achieved the goal. The statement that an entity has achieved its goal is always in comparison to the state of entity at the time when the process to achieve the goal begun.
4. Beliefs change over period of time.
5. Facts are discovered not invented. They are present whether we know about them or not.
6. Facts belong to Closed-World semantics.
7. Beliefs belong to Open-World semantics and as discussed earlier they are constructed and can be destroyed as well.

I still have long way to go on this way. Any pointers from readers would be good.

PS: Its been almost 2 months since I had my last post on this blog. But I plan to come back in full swing soon and start posting regularly.

Until next time... !!!

Predicate and URIs

While going through different papers I realized that almost every research paper has different functions that do some common operations and work on two objects. Say isMotherOf(x,y) could be mother(x,y) and so on. Now the questions arises that if there are many such predicates exist in different knowledge base then how will someone know that they are related and they virtually do the same thing.

The Predicates are like function or relation-builder as they establish relationship between two objects. So we can very well say that the predicates are the base for our reasoning mechanism or determining what the two objects are all about. It also plays an important role in the context definition of the two objects.

This gives me a strong point to put forward the predicate being a URI so that two knowledgebase if they are using the same predicate or relation then they do mean the same thing. Using this principle a Reasoning Engine can be developed that can extract the meaning of the statements / facts etc in the system. If we design a system on this principle then the amount of ambiguity we need to deal with will be less.

The RDF facilitates the Predicates to be both URI and simple text, but in long run the simple text might look flexible or simple to work with but more people will use URIs for the predicate in RDF. Removing the ambiguity once and for all is a distant dream though. Even though we follow these principles, we will still have some duplicate predicates in the system. But somewhere along the line we need to develop a mapping that will assign aliases for both the predicates and based on popularity the less used one can be phased out in due course.

Until Next Time.....

Entities and Representing Facts

In my previous post I started a discussion about Inferencing and Facts. The biggest challenge we have is how to represent these facts in the computer system. Last week I was reading the paper "A Library of Generic Concepts for Composing Knowledge Bases" by Ken Barker, Bruce Porter and Peter Clark, Proceedings of K-CAP 01, October 22-23 2001.

In this paper the authors make a classification between Entities and Events. Entities are things that are and Events are things that happen. Events are states and actions. States are static situation brought about or changed by actions.

To elaborate further on this Entities are the state information or the facts. Actions apply on those entities. So if we revisit our earlier post the facts can be represented as attributes of an object. Like Sun rises in east can be represented as Rising Direction (Predicate) attribute of Sun (Subject) with a value East (an instance of type direction). Similarly we can also represent other facts mentioned in the earlier post.

Any second thought????

Until Next Time ....

Inferencing and Facts

In my previous post I started a discussion on Reasoning and Inferencing. Going by very definition of inferencing it is an act of attaining conclusion based on certain facts. But what is fact? The facts could be

• Universal Truths like Sun rises in east, it is winter in Australia.
• Statements about an object instance. Toyota Yaris, YRS Rego ABC 123. Here we are considering only about one car.
• A general statement about all objects of one type. Toyota cars are better than Honda in terms of easy maintenance (I am not going to start car manufacturer war here).
• Statement applicable to more than one type of object. If battery is down then none of the battery operated or petrol vehicle will start.
  

But the actual problem is not what the fact is. The problem begins when we want to store the fact for computer systems to understand and reason. We need to store them in our KnowledgeBase which is nothing else but a collection of facts about one or more entities. To store facts in KB we need to have few issues sorted out like:

1. How do we represent the facts in Computer System?
2. How do we link the facts to the entities they describe about?
3. How do we retrieve the facts and relate them to the entities?
4. How do we find all the facts that are known about an entity?

There are many such buzzing questions which needs to be answered before we go ahead with building a system that infers these facts. I would like to get an opinion from the readers as what their opinion is.

Until Next Time...!!!