KR 2024 homework part 1 - Redigeerimiste ajalugu

Tammet: /* Using large datasets: logictools vs command line reasoner gkc */

2024-02-21T09:51:22Z

Using large datasets: logictools vs command line reasoner gkc

←Vanem redaktsioon		Redaktsioon: 21. veebruar 2024, kell 11:51
139. rida:		139. rida:
	Thus I'd recommend to download the full-powered version of the reasoner used in logictools from https://github.com/tammet/gkc : it is best to use the somewhat older release https://github.com/tammet/gkc/releases/tag/v0.6.0 which has the same codebase as logictools. Just take the provided windows, linux or macos binary: no need to compile yourself.		Thus I'd recommend to download the full-powered version of the reasoner used in logictools from https://github.com/tammet/gkc : it is best to use the somewhat older release https://github.com/tammet/gkc/releases/tag/v0.6.0 which has the same codebase as logictools. Just take the provided windows, linux or macos binary: no need to compile yourself.

	A rather thorough tutorial of gkc with examples is README.md here: https://github.com/tammet/gkc/~~tree~~/master/Examples		A rather thorough tutorial of gkc with examples is README.md here: https://github.com/tammet/gkc/blob/master/Examples/README.md

	= Optional: additional datasets =		= Optional: additional datasets =

Tammet: /* Using large datasets: logictools vs command line reasoner gkc */

2024-02-21T09:50:48Z

Using large datasets: logictools vs command line reasoner gkc

←Vanem redaktsioon		Redaktsioon: 21. veebruar 2024, kell 11:50
139. rida:		139. rida:
	Thus I'd recommend to download the full-powered version of the reasoner used in logictools from https://github.com/tammet/gkc : it is best to use the somewhat older release https://github.com/tammet/gkc/releases/tag/v0.6.0 which has the same codebase as logictools. Just take the provided windows, linux or macos binary: no need to compile yourself.		Thus I'd recommend to download the full-powered version of the reasoner used in logictools from https://github.com/tammet/gkc : it is best to use the somewhat older release https://github.com/tammet/gkc/releases/tag/v0.6.0 which has the same codebase as logictools. Just take the provided windows, linux or macos binary: no need to compile yourself.

	A rather thorough tutorial of gkc with examples is here: https://github.com/tammet/gkc/tree/master/Examples		A rather thorough tutorial of gkc with examples is README.md here: https://github.com/tammet/gkc/tree/master/Examples

	= Optional: additional datasets =		= Optional: additional datasets =

Tammet: /* Using large datasets: logictools vs command line reasoner gkc */

2024-02-21T09:50:16Z

Using large datasets: logictools vs command line reasoner gkc

←Vanem redaktsioon		Redaktsioon: 21. veebruar 2024, kell 11:50
138. rida:		138. rida:

	Thus I'd recommend to download the full-powered version of the reasoner used in logictools from https://github.com/tammet/gkc : it is best to use the somewhat older release https://github.com/tammet/gkc/releases/tag/v0.6.0 which has the same codebase as logictools. Just take the provided windows, linux or macos binary: no need to compile yourself.		Thus I'd recommend to download the full-powered version of the reasoner used in logictools from https://github.com/tammet/gkc : it is best to use the somewhat older release https://github.com/tammet/gkc/releases/tag/v0.6.0 which has the same codebase as logictools. Just take the provided windows, linux or macos binary: no need to compile yourself.

			A rather thorough tutorial of gkc with examples is here: https://github.com/tammet/gkc/tree/master/Examples

	= Optional: additional datasets =		= Optional: additional datasets =

Tammet: /* Ideas for writing your own rules */

2024-02-12T15:43:18Z

Ideas for writing your own rules

←Vanem redaktsioon		Redaktsioon: 12. veebruar 2024, kell 17:43
116. rida:		116. rida:
	* Finding data from people-in-estonia.txt for persons active in created-in-estonia.txt. Finding people born nearby active in the same movies. Etc.		* Finding data from people-in-estonia.txt for persons active in created-in-estonia.txt. Finding people born nearby active in the same movies. Etc.
	* Convert birth dates like <i>yago:Endel_Ruberg schema:birthDate "1917-05-21T00:00:00Z"^^xsd:dateTime</i> to simple integers and use the built-in arithmetic of th e reasoner (see "About" -> "Special symbols and additional constructions" in logictools) to filter out suitable people. Who is surely not alive any more? Who are roughly of the same age and have something more in common?		* Convert birth dates like <i>yago:Endel_Ruberg schema:birthDate "1917-05-21T00:00:00Z"^^xsd:dateTime</i> to simple integers and use the built-in arithmetic of th e reasoner (see "About" -> "Special symbols and additional constructions" in logictools) to filter out suitable people. Who is surely not alive any more? Who are roughly of the same age and have something more in common?
			* Converting triplets in the dataset <i>triple(a,b,c)</i> where the first and second argument should conceptually strictly determine the third (like when c is a birthdate) to equalities like <i>b(a)=c</i> instead and then using terms and equalities in your rules for such cases.
	* Generating trips with actual paths shown in answers: you will need function term arguments in your predicates for this, see the example from the first lecture:		* Generating trips with actual paths shown in answers: you will need function term arguments in your predicates for this, see the example from the first lecture:

Tammet: /* Ideas for writing your own rules */

2024-02-12T15:39:26Z

Ideas for writing your own rules

←Vanem redaktsioon		Redaktsioon: 12. veebruar 2024, kell 17:39
111. rida:		111. rida:
	Some ideas, including somewhat crazy ones:		Some ideas, including somewhat crazy ones:

	* Categorizing objects into larger categories, using the transivity of rdf:type (you have to write your own rule for the transitivity). ~~Convert~~ yago-taxonomy.txt to rules and use this for larger categories.		* Categorizing objects into larger categories, using the transivity of rdf:type (you have to write your own rule for the transitivity). You may also (strictly optional) convert yago-taxonomy.txt to rules and use this for larger categories.
	* What city/town/lake/island is inside what, according to located-in-estonia.txt. What can you derive from this, say, using transitivity of <i>inside</i>?		* What city/town/lake/island is inside what, according to located-in-estonia.txt. What can you derive from this, say, using transitivity of <i>inside</i>?
	* Who was born where and how could they potentially travel with the boat to a place another person was born :)		* Who was born where and how could they potentially travel with the boat to a place another person was born :)

Tammet: /* Ideas for writing your own rules */

2024-02-12T15:32:55Z

Ideas for writing your own rules

@@ 115. rida: / 115. rida: @@
 * Who was born where and how could they potentially travel with the boat to a place another person was born :)
 * Finding data from people-in-estonia.txt for persons active in created-in-estonia.txt. Finding people born nearby active in the same movies. Etc.
 * Convert birth dates like <i>yago:Endel_Ruberg       schema:birthDate        "1917-05-21T00:00:00Z"^^xsd:dateTime</i> to simple integers and use the built-in arithmetic of th e reasoner (see "About" -> "Special symbols and additional constructions" in logictools) to filter out suitable people. Who is surely not alive any more? Who are roughly of the same age and have something more in common?
 = Using large datasets: logictools vs command line reasoner gkc =

Tammet: /* Optional: additional datasets */

2024-02-12T15:29:43Z

Optional: additional datasets

←Vanem redaktsioon		Redaktsioon: 12. veebruar 2024, kell 17:29
132. rida:		132. rida:
	with the "wd:" defined above as "http://www.wikidata.org/entity/", thus leading to pages like http://www.wikidata.org/entity/Q2627792 . Now, looking at the source of this page, you find rows like <code><link rel="alternate" href="https://www.wikidata.org/wiki/Special:EntityData/Q2627792.nt" type="application/n-triples"></code> with the link		with the "wd:" defined above as "http://www.wikidata.org/entity/", thus leading to pages like http://www.wikidata.org/entity/Q2627792 . Now, looking at the source of this page, you find rows like <code><link rel="alternate" href="https://www.wikidata.org/wiki/Special:EntityData/Q2627792.nt" type="application/n-triples"></code> with the link
	https://www.wikidata.org/wiki/Special:EntityData/Q2627792.nt leading to a large set of triplets related to Lake Peipsi! Most of these represent some specific complex encodings of this wikidata web page itself, but several are actually about Peipsi.		https://www.wikidata.org/wiki/Special:EntityData/Q2627792.nt leading to a large set of triplets related to Lake Peipsi! Most of these represent some specific complex encodings of this wikidata web page itself, but several are actually about Peipsi.

			A list of well-known and used large "generic" fact and knowledge bases can be found in http://lambda.ee/wiki/Teadmiste_formaliseerimine#Block_3:_General-knowledge_databases . You may want to have a look at these, but beware: obviously it takes time to understand and process. Another cool source is [https://www.kaggle.com/datasets kaggle.]

Tammet: /* Data */

2024-02-12T13:34:59Z

Data

←Vanem redaktsioon		Redaktsioon: 12. veebruar 2024, kell 15:34
9. rida:		9. rida:
	= Data =		= Data =

	Riina took the large datasets from https://yago-knowledge.org/ and prepared relatively small selections (all about something Estonian) from this data. The link to the files is [https://cs.taltech.ee/staff/riina.maigre/iti8700/lab1/ here]. The data is presented as plain triplets, no fancy encoding (except namespaces) ~~are~~ involved.		Riina took the large datasets from https://yago-knowledge.org/ and prepared relatively small selections (all about something Estonian) from this data. The link to the files is [https://cs.taltech.ee/staff/riina.maigre/iti8700/lab1/ here]. The data is presented as plain triplets, no fancy encoding (except namespaces) is involved.

	First, please download the files and explore them a bit. Then convert the files to the format our reasoner gk (or its web version http://logictools.org) can eat. Write a program for this! Trying to just replace/filter stuff using an editor will become very cumbersome soon.		First, please download the files and explore them a bit. Then convert the files to the format our reasoner gk (or its web version http://logictools.org) can eat. Write a program for this! Trying to just replace/filter stuff using an editor will become very cumbersome soon.

Tammet – 12. veebruar 2024, kell 13:34

2024-02-12T13:34:25Z

←Vanem redaktsioon		Redaktsioon: 12. veebruar 2024, kell 15:34
1. rida:		1. rida:
	You will have to write a small program to convert/filter data to a suitable format for experimenting with a logical reasoner, and then write ca 10 nontrivial rules for answering questions. Finally, experiment with the reasoner on this data + rules and make a small presentation of your data, rules, successes and failures.		You will have to write a small program to convert/filter data to a suitable format for experimenting with a logical reasoner, and then write ca 10 nontrivial rules for answering questions. Finally, experiment with the reasoner on this data + rules and make a small presentation of your data, rules, successes and failures.

			The presentation does not have to be made with special slides and a long writeup (although this is also OK). You are expected to show the data, rules and results and briefly explain your ideas, experiments and the work process. Just using an editor for showing this stuff is OK. Best if you can also make a small demo with the reasoner actually running and proving some of the queries.

	Not everything you try out needs to work: some failures are also interesting.		Not everything you try out needs to work: some failures are also interesting.

Tammet – 12. veebruar 2024, kell 13:19

2024-02-12T13:19:45Z

←Vanem redaktsioon		Redaktsioon: 12. veebruar 2024, kell 15:19
21. rida:		21. rida:
	<i>http://www.w3.org/1999/02/22-rdf-syntax-ns#</i>: the abbreviations make the symbols unique enough for our purposes.		<i>http://www.w3.org/1999/02/22-rdf-syntax-ns#</i>: the abbreviations make the symbols unique enough for our purposes.

	The predicate <i>triple</i> is really arbitrary: you may use any name you like. You may also use the fourth argument for type, if you wish (like "string" in ~~the~~ case ~~above~~). Importantly, there are subtle differences between writing constants like <i>yago:Lake_Peipsi</i> with or without quotation marks:		The predicate <i>triple</i> is really arbitrary: you may use any name you like. You may also use the fourth argument for type, if you wish (like "string"/"integer"/"id", in case it helps). Importantly, there are subtle differences between writing constants like <i>yago:Lake_Peipsi</i> with or without quotation marks:
	* Without quotation the reasoner does not assume that two different constants necessarily mean different objects. Saying <i>yago:Lake_Peipsi = yago:Lake_Peipus</i> does not lead to a contradiction. Also, non-ascii symbols are generally not ok for non-quoted constants.		* Without quotation the reasoner does not assume that two different constants necessarily mean different objects. Saying <i>yago:Lake_Peipsi = yago:Lake_Peipus</i> does not lead to a contradiction. Also, non-ascii symbols are generally not ok for non-quoted constants.
	* Quotation marks make the reasoner to treat constants as strings, and thus <i>"yago:Lake_Peipsi" = "yago:Lake_Peipus"</i> is a contradiction. Also, non-ascii symbols are OK.		* Quotation marks make the reasoner to treat constants as strings, and thus <i>"yago:Lake_Peipsi" = "yago:Lake_Peipus"</i> is a contradiction. Also, non-ascii symbols are OK.