Update README.md

README.md

@@ -149,17 +149,22 @@ We have used the dataset to evaluate the engines [GeoQA2](https://github.com/AI-
 ##### Additional benchmark results exist and we are working on publishing them. Until then, if you want to see more please send a message at: 
 `s[dot]kefalidis[at]di[dot]uoa[dot]gr`
 
+
 ## Materialization and Transpiler
 
 To improve the time performance of query execution, we pre-computed and materialized certain relations between entities in the YAGO2geo KG. 
 
-The geospatial relations *within*, *crosses*, *intersects* and *borders* (and their extensions, e.g., *overlaps* and *covers*) are the most expensive ones to be computed. While *north*, *south*, *east and *west* are easily computed. Hence, we materialized these relations.
+The geospatial relations *within*, *crosses*, *intersects* and *borders* (and their extensions, e.g., *overlaps* and *covers*) are the most expensive ones to be computed. While *north*, *south*, *east* and *west* are easily computed. Hence, we materialized these relations.
+
+To easily utilize these materialized relations, please see the [GitHub repository](https://github.com/AI-team-UoA/GeoQuestions1089/).
+
+## RDF Store
 
-To utilize these materialized relations, please see the [GitHub repository](https://github.com/AI-team-UoA/GeoQuestions1089/).
+To run the experiments and generate the answers for the gold and generated queries we used GraphDB. Because GraphDB does not support stSPARQL functions, we have [extended the GeoSPARQL plugin of GraphDB](https://github.com/SKefalidis/graphdb-geosparql-plugin).
 
 ## Notes
 
-### About the definition of near for distance calulations
+### About the definition of near for distance calculations
 We decided to define *near* based on the concept used. This is consistent with the definition of near in [GeoQuestions201](https://geoqa.di.uoa.gr/geospatial_gold_standard.html).
 
 | Near to | Distance |