Wikidata models assertions of facts about things and it has a very powerful system for writing queries to get at the facts and relationships you are interested in.
Here are some examples of what you can do with Wikidata:
https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/...
> knowledge is encoded in machine readable format and that we can start to write programs over this knowledge graph
But surely that abilty has been the goal of wikidata from the start?
The example they give is the constructor:
rank(SanFrancisco, city, 4, population, California)
And the English renderer will output:
"San Francisco is the fourth largest city by population in California."
Do the Hebrew Wikipedia and the Arabic Wikipedia agree on the status of Israel?
If they don’t agree, perhaps they can agree to disagree and we can encode that fact instead.
Agree to disagree is like saying there is no right side in this matter which is okay for topics where there isn't. Many topics however are not a matter of perspective, they are a matter of who is factually right.
IMO in such a case agreeing to disagree can often be destructive, because it legitimises a position which is factually wrong and constructs an illusion of balance where there is none.
If one side says it rains and the other says it doesn't, agreeing to disagree is wrong. If there is disagreement about what the facts mean, then sometimes both perspective can be true at the same time. This is however not as often the case as I wish it would be..
No. Agreeing to disagree is accepting, that a subject is disputed with different, even contradicting opinions.
An AI could in theory extract both versions and present them as disputed. Meaning, there are different definitions of a word and the correctness of facts.
And "raining or not" is also not as simple as you think. A person from spain will consider a certain state as raining, which a british person might see as some humidity in the air ..
Option 1: we call it a controversy and make it sound like because some people don’t believe in it means it might not be correct.
Option 2: we state upfront that the theory of evolution is correct but link to a “incorrect but competing viewpoint” of creationism.
Option 3: we create three articles: one about the theory of evolution, one about creationism, and one about the disagreements between the creationists and the rest of the modern world.
I like option 3 best as it is the most complete picture of the three, and all it requires is the abstract concept of controversy or disagreement. I don’t know how you encode “dumbass” in this new format but it might be a useful concept to explain to aliens if they decide to visit Earth.
A theory is distinct from a hypothesis, but surely it isn't itself a fact either.
Wouldn't it be better to say that the theory of evolution explains a lot of facts, which we may also call (observed) evolution? Really, aren't we just calling two related concepts "evolution"?
There are a number of theories related to gravity. That doesn’t mean gravity isn’t a fact, it just means we don’t 100% understand how it works in all situations (eg quantum).
Similar for evolution - there are various scientific theories about the origins of species. And it is absolutely the case that we don’t know 100% how we got from Big Bang to here, thus the theories are still theories. If you just want to point to Darwinism and say fact, you’d be doing a large disservice to us all.
Only when relations are defined in a kind of Prolog style in those examples it will be usable as knowledge about things other than language.
A computer might spit out texts which it guessed are connected to some question you ask it though. Does not mean it understands the relations of things.
But when can we ever really say "a machine understands" something? So perhaps there is not much of a difference?
In my point of view, the problem here is that you could say something like "'water' and 'heat' produces 'steam'", but knowledge is never that simple, and understanding of that information is even more complicated.
I would think that Abstract Wikipedia is not the first people trying to solve such a problem, and I am very curious to see what they come up with.
EDIT: Looks like they have an example: https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Examples
> The goal of Abstract Wikipedia is to let more people share in more knowledge in more languages. Abstract Wikipedia is an extension of Wikidata. In Abstract Wikipedia, people can create and maintain Wikipedia articles in a language-independent way. A Wikipedia in a language can translate this language-independent article into its language. Code does the translation.
from https://meta.wikimedia.org/wiki/Abstract_Wikipedia
Will this mean that knowledge is encoded in machine readable format and that we can start to write programs over this knowledge graph? This is huge.