Until now our queries essentially had just one variable, even if additional variables were declared for the label and\/or description of the item. Now we will look at queries with more variables.
The following query retrieves items that are part of the Star Wars film series, and the director of each film.<\/p>\n\n\n\n
#Star Wars films\n\nSELECT ?item ?itemLabel ?director\nWHERE \n{ \n ?item wdt:P179 wd:Q22092344. # item is part of the series Star Wars (film series)\n ?item wdt:P57 ?director. # item\u2019s director property\u2019s value is collected by the director variable\n SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE]". }\n}<\/pre><\/div>\n\n\n\nQuery explanation<\/h3>\n\n\n\n
In the SELECT section we have the variables ?item and ?director, as well as ?itemLabel which retrieves the label for ?item.<\/p>\n\n\n\n
In the WHERE section, on lines 6 and 7, we see the pattern matching conditions:
?item wdt:P179 wd:Q22092344.
?item wdt:P57 ?director.
SPARQL seeks Wikidata items with statements that match the pattern defined in the WHERE section. So, as before, our WHERE section’s first line says, “Find me items that have a statement with a P179 property (part of a series) with the value Q22092344 (Star Wars (film series))”.
The second line says, “Then for each of those items, find me their P57 property (director) and put its value in the variable ?director.”
As we’ve seen<\/a>, there is an implicit AND between each statement in the WHERE section, i.e. only patterns that match\u00a0all<\/strong>\u00a0statements will be returned by this query.\u00a0 <\/p>\n\n\n\nNow let’s run the query:<\/p>\n\n\n\n