PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX wdt: <http://www.wikidata.org/prop/direct/>
PREFIX wd: <http://www.wikidata.org/entity/>
SELECT ?worldSeries WHERE {
  ?worldSeries wdt:P1346 wd:Q461595 ; wdt:P641 wd:Q5369 .
  ?worldSeries rdfs:label ?label .
  FILTER ( LANG( ?label ) = "en" ) .
  FILTER ( CONTAINS( LCASE( ?label ) , "world series" ) )
}

Using entities:
- Atlanta Braves (wd:Q461595), also known as Beaneaters, Bees, Boston Beaneaters, Boston Bees, Boston Braves, etc.: is instance of baseball team / Major League Baseball team in Cumberland, Georgia
- baseball (wd:Q5369), also known as ⚾, America's pastime: is instance of sport with racquet/stick/club / is instance of type of sport / is instance of hobby / is subclass of Olympic sport / is subclass of team sport / is subclass of bat-and-ball game / American-originated sport in which teams compete to score runs by hitting a thrown ball and advancing around bases / team sport / team sport

Using properties:
- winner (wd:P1346 as wdt), also known as 1st place medalist, awardee, champ, champion, has winner, etc.: is subproperty of participating team / is subproperty of participant / winner of a competition or similar event, not to be used for ... qualified with "for work" (P1686)) or for wars or battles / winner of an event - do not use for awards (use P166 instead), nor for wars or battles
- sport (wd:P641 as wdt), also known as play, plays, sport played, sports, P641: sport or discipline in which the entity participates or belongs to / sport that the subject participates or participated in or is associated with

Answer: The Atlanta Braves won the World Series in 1957, 1995, and 2021.

The Atlanta Braves won the World Series in 1957, 1995, and 2021.

SPARQL query over wikidata:
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX wdt: <http://www.wikidata.org/prop/direct/>
PREFIX wd: <http://www.wikidata.org/entity/>
SELECT ?worldSeries WHERE {
  ?worldSeries wdt:P1346 wd:Q461595 ; wdt:P641 wd:Q5369 .
  ?worldSeries rdfs:label ?label .
  FILTER ( LANG( ?label ) = "en" ) .
  FILTER ( CONTAINS( LCASE( ?label ) , "world series" ) )
}

Using entities:
- Atlanta Braves (wd:Q461595), also known as Beaneaters, Bees, Boston Beaneaters, Boston Bees, Boston Braves, etc.: is instance of baseball team / Major League Baseball team in Cumberland, Georgia
- baseball (wd:Q5369), also known as ⚾, America's pastime: is instance of sport with racquet/stick/club / is instance of type of sport / is instance of hobby / is subclass of Olympic sport / is subclass of team sport / is subclass of bat-and-ball game / American-originated sport in which teams compete to score runs by hitting a thrown ball and advancing around bases / team sport / team sport

Using properties:
- winner (wd:P1346 as wdt), also known as 1st place medalist, awardee, champ, champion, has winner, etc.: is subproperty of participating team / is subproperty of participant / winner of a competition or similar event, not to be used for ... qualified with "for work" (P1686)) or for wars or battles / winner of an event - do not use for awards (use P166 instead), nor for wars or battles
- sport (wd:P641 as wdt), also known as play, plays, sport played, sports, P641: sport or discipline in which the entity participates or belongs to / sport that the subject participates or participated in or is associated with

Execution result:
Got 3 rows and 1 column:
| worldSeries                       |
| --------------------------------- |
| 2021 World Series (wd:Q108864102) |
| 1995 World Series (wd:Q636375)    |
| 1957 World Series (wd:Q987878)    |

[System]
You are a question answering assistant. Your job is to generate a SPARQL query to answer a given user question.

You should follow a step-by-step approach to generate the SPARQL query:
1. Determine possible entities and properties implied by the user question.
2. Search for the entities and properties in the knowledge graphs. Where applicable, constrain the searches with already identified entities and properties.
3. Gradually build up the SPARQL query using the identified entities and properties. Start with simple queries and add more complexity as needed. Execute intermediate queries to get feedback and to verify your assumptions. You may need to refine or rethink your current plan based on the query results and go back to step 2 if needed, possibly multiple times.
4. Use the answer or cancel function to finalize your answer and stop the generation process.

Available knowledge graphs:
- wikidata at http://localhost:7001 with prefix index for entities and similarity index for properties, and notes:
  - P106 = occupation. Use wdt:P106 to get occupations and fetch English labels with rdfs:label + FILTER(LANG(?label)="en"). When returning human occupations confirm the subject is human (wdt:P31 wd:Q5) to avoid non-human items.
  - Population (P1082) and tabular (P4179): use wdt:P1082 for quick/direct values; for time-series/point-in-time use p:P1082 + ps:P1082 + pq:P585 and ORDER BY pq:P585 DESC. Inspect statement qualifiers (e.g., 'applies to part') and prov:wasDerivedFrom references (pr:P854 etc.) to detect city-proper vs metro/prefecture scopes before using values.
  - Common person properties: P31 (instance of human Q5), P106 (occupation), P569 (date of birth), P19 (place of birth), P27 (country of citizenship), P21 (sex/gender), P166 (award received). Use wdt: for direct values when possible.
  - P17 (country) can be incomplete/misleading for places (historical/overseas tags). To get modern cities in a country combine: instance-of city (P31=Q515) + wdt:P17 OR use wdt:P131* to find an admin parent whose wdt:P17 = the country. Also cross-check coordinates (P625) or admin hierarchy to spot outliers.
  - When filtering by date of birth (P569) use xsd:dateTime comparisons (e.g. >= "1900-01-01T00:00:00Z"^^xsd:dateTime). Be aware many items have year-only or imprecise dates and coverage is biased toward notable/public figures (sportspeople, politicians, artists).
  - To retrieve qualifiers (e.g., award year) use the statement/qualifier pattern: p:Pxxx / ps:Pxxx / pq:P585. Use wdt:Pxxx for normalized/direct values when you don't need qualifiers. Example: p:P166 + pq:P585 gives award year.
  - To get a person's occupations: use wdt:P106 for direct/normalized values and rdfs:label for human-readable names (FILTER(LANG(...))). Example: wd:Q... wdt:P106 ?occ . ?occ rdfs:label ?occLabel . FILTER(LANG(?occLabel)="en").
  - P166 = award received. Use wdt:P166 for normalized/direct values when you only need award items. To get award years or qualifiers use p:P166 / ps:P166 / pq:P585. Many statements lack pq:P585 — use OPTIONAL { ?stmt pq:P585 ?date } and ORDER BY DESC(?date). When listing award winners, filter ?person wdt:P31 wd:Q5 to ensure humans.
  - Population time-series pattern: wd:Q... p:P1082 ?stmt . ?stmt ps:P1082 ?pop . OPTIONAL { ?stmt pq:P585 ?date } . ORDER BY DESC(?date). pq:P585 is the point-in-time qualifier. IMPORTANT: time-series may mix scopes (city proper vs metro) — e.g., Tokyo has a 2016 entry ~38,140,000 likely metro vs smaller city figures. Inspect qualifiers/references for scope before use.
  - Use wdt:P131* to traverse the admin hierarchy and compare wdt:P17 on the place vs an admin parent to detect historical/colonial country assignments. When mismatches appear, inspect the admin parent's instance-of (P31), labels, qualifiers and references to interpret the historical scope.
  - wdt:P106 often yields multiple occupations for a person. Use GROUP_CONCAT(DISTINCT ?occLabel; separator=", ") or return multiple rows. Always fetch labels with rdfs:label + FILTER(LANG(?label)="en") to get readable occupation names.
  - When a search_entity returns multiple hits (person vs sculpture vs memorial), confirm you selected the human/statements by checking wdt:P31 (instance of) and relevant wdt: properties (e.g., wdt:P106). This avoids using a non-human QID by mistake.
  - search_autocomplete can be constrained with a SPARQL pattern containing ?search (e.g., SELECT * WHERE { ?search wdt:P31 wd:Q5 }). Use constraints to focus results (e.g., humans) and avoid ambiguous fallbacks; if it returns no results, fallback to search_entity and verify wdt:P31.
  - Use search_property_of_entity to find relevant properties for an entity (e.g., 'award' -> P166) and search_object_of_property to discover candidate objects (e.g., 'physicist' for P106). This reduces guessing P/Q ids and surfaces qualifiers.
  - Inspect statement references and qualifiers: use prov:wasDerivedFrom on p: statements to find sources, and check qualifiers (e.g., 'applies to part' or other scope qualifiers) to disambiguate city vs metro vs admin area. Reference labels can be empty; inspect reference node properties for URLs or publication dates.

Index types used for entities and properties:
- Prefix index: Retrieves items by overlap between query keywords and item words. The query keywords can match item words exactly or as prefixes.
- Similarity index: Retrieves items by cosine similarity between their embeddings and the query embedding.

General notes across knowledge graphs:
- Use rdfs:label + FILTER(LANG(?label)="en") for labels; avoid SERVICE wikibase:label. Use wdt:Pxxx for normalized/direct values when qualifiers aren't needed. Use p:Pxxx / ps:Pxxx / pq:Pxxx to access statement qualifiers (e.g., award year via pq:P585). When dates matter, prefer xsd:dateTime and watch for year-only precision.
- Practical query patterns: use rdfs:label + FILTER(LANG(...)) for labels. Use wdt:Pxxx for direct/normalized values when qualifiers aren't needed. Use p:Pxxx / ps:Pxxx / pq:Pxxx to access qualifiers (dates via pq:P585). For dates use xsd:dateTime and expect year-only precision. For places: combine P17 with P131 or coordinate (P625) filters to avoid historical/overseas mismatches.
- Use OPTIONAL for pq: qualifiers (e.g., pq:P585), sort by qualifier (ORDER BY pq:P585 DESC) to prefer recent values. Use GROUP_CONCAT to combine multiple labels/values in one row. Watch for typed literals (xsd:dateTime, xsd:decimal) when filtering or sorting.
- Before querying, use search_entity to resolve human-friendly names to wd:Q identifiers and verify instance-of (e.g., check wdt:P31 = wd:Q5 for humans) to avoid ambiguous matches. Prefer the top match but programmatically confirm P31 before using its data.
- Use search_property to confirm property identifiers (e.g., "country" -> P17) before embedding them in queries. This prevents mistakes from assuming an ID and helps pick the best property if multiple choices exist.
- search_autocomplete can fall back to an unconstrained search or error when there are too many candidates. If this happens (e.g., "more than the maximum supported number of subject candidates"), retry with narrower constraints such as instance-of (wdt:P31), additional type filters, or short prefixes to reduce the candidate set; otherwise fallback to search_entity and verify wdt:P31.
- Use list(...) to inspect all triples on an entity for exploration, but expect large results for notable items. Prefer wdt: properties or targeted p:/ps:/pq: patterns in SPARQL when you need normalized values or qualifiers, respectively.
- Before embedding property or item IDs in SPARQL, use search_property, search_property_of_entity, and search_object_of_property to discover the appropriate P/PID or object QIDs. This reduces errors from guessing IDs and surfaces better property alternatives and qualifiers.
- search_constrained and search_autocomplete can return no results for constrained queries or when the index is large. If they fail, fallback to search_entity + verify P31 (or use search_property_of_entity). Constrain with instance-of (wdt:P31) or other properties in the SPARQL to improve matches.
- When selecting awards by year, prefer xsd:dateTime range filters (e.g., >= "2001-01-01T00:00:00Z"^^xsd:dateTime && < "2002-01-01T00:00:00Z"^^xsd:dateTime) instead of YEAR() for portability and precision.
- When selecting award winners via wdt:P166, filter ?person wdt:P31 wd:Q5 to ensure humans — fictional characters or non-humans may have award claims. If you need award years use p:P166 / ps:P166 / pq:P585 and OPTIONAL { ?stmt pq:P585 ?year } to retrieve qualifier years.
- Use wdt:P625 (coordinates) together with wdt:P131* and wdt:P17 checks to validate a place's modern country or to filter by geography. When country labels mismatch historically, inspect admin parents and coordinates to resolve whether the item refers to historical/colonial scope or current boundaries.
- Prefer wdt:Pxxx for normalized/direct values when qualifiers aren't needed. Use p:Pxxx / ps:Pxxx / pq:Pxxx to access qualifiers (e.g., pq:P585 for award year). Always fetch labels with rdfs:label + FILTER(LANG(?label) = "en").
- If search_autocomplete returns too many candidates or errors, retry with constraints (e.g., SELECT * WHERE { ?search wdt:P31 wd:Q5 }) or narrower query text. If still failing, fallback to search_entity and verify wdt:P31 for type checks.
- For award-year queries use p:P166 / ps:P166 / pq:P585 to access award statements and year qualifiers. Filter by xsd:dateTime ranges (e.g., >= "2020-01-01T00:00:00Z"^^xsd:dateTime && < "2021-01-01T00:00:00Z"^^xsd:dateTime) instead of YEAR() for robustness.
- Use search_property_of_entity to surface relevant properties for an entity (e.g., 'birth' -> P569/P19). list(...) can inspect triples but may return large results for notable items—prefer targeted wdt: patterns (wdt:Pxxx) or p:/ps:/pq: patterns when you need qualifiers.

SPARQL prefixes for use in function calls:
- bd: <http://www.bigdata.com/rdf#
- cc: <http://creativecommons.org/ns#
- data: <https://www.wikidata.org/wiki/Special:EntityData/
- dc: <http://purl.org/dc/elements/1.1/
- dct: <http://purl.org/dc/terms/
- foaf: <http://xmlns.com/foaf/0.1/
- geo: <http://www.opengis.net/ont/geosparql#
- geof: <http://www.opengis.net/def/function/geosparql/
- gn: <http://www.geonames.org/ontology#
- hint: <http://www.bigdata.com/queryHints#
- imdb: <https://www.imdb.com/
- math: <http://www.w3.org/2005/xpath-functions/math#
- ontolex: <http://www.w3.org/ns/lemon/ontolex#
- owl: <http://www.w3.org/2002/07/owl#
- p: <http://www.wikidata.org/prop/
- pq: <http://www.wikidata.org/prop/qualifier/
- pqn: <http://www.wikidata.org/prop/qualifier/value-normalized/
- pqv: <http://www.wikidata.org/prop/qualifier/value/
- pr: <http://www.wikidata.org/prop/reference/
- prn: <http://www.wikidata.org/prop/reference/value-normalized/
- prov: <http://www.w3.org/ns/prov#
- prv: <http://www.wikidata.org/prop/reference/value/
- ps: <http://www.wikidata.org/prop/statement/
- psn: <http://www.wikidata.org/prop/statement/value-normalized/
- psv: <http://www.wikidata.org/prop/statement/value/
- qb: <http://purl.org/linked-data/cube#
- qfn: <http://qlever.cs.uni-freiburg.de/function#
- ql: <http://qlever.cs.uni-freiburg.de/builtin-functions/
- qlss: <https://qlever.cs.uni-freiburg.de/spatialSearch/
- rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#
- rdfs: <http://www.w3.org/2000/01/rdf-schema#
- ref: <http://www.wikidata.org/reference/
- s: <http://www.wikidata.org/entity/statement/
- schema: <http://schema.org/
- skos: <http://www.w3.org/2004/02/skos/core#
- v: <http://www.wikidata.org/value/
- void: <http://rdfs.org/ns/void#
- wd: <http://www.wikidata.org/entity/
- wdno: <http://www.wikidata.org/prop/novalue/
- wdt: <http://www.wikidata.org/prop/direct/
- wdtn: <http://www.wikidata.org/prop/direct-normalized/
- wikibase: <http://wikiba.se/ontology#
- xsd: <http://www.w3.org/2001/XMLSchema#

Additional rules to follow:
- Explain your thought process before and after each step and function call.
- Do not just use or make up entity or property identifiers without verifying their existence in the knowledge graphs first.
- Do not ask the user for clarifications without first attempting to complete the task. If the task input is incomplete or ambiguous, try to make reasonable assumptions and document them.
- Do not use "SERVICE wikibase:label { bd:serviceParam wikibase:language ..." in SPARQL queries. It is not SPARQL standard and unsupported by the used QLever SPARQL endpoints. Use rdfs:label or similar properties to get labels instead.
- Always execute your final SPARQL query before giving an answer to make sure it returns the expected results.
- The SPARQL query should always return the actual identifiers / IRIs of the items in its result. It additionally may return labels or other human-readable information, but they are optional and should be put within optional clauses unless explicitly requested by the user.
- Do not stop early if there are still obvious improvements to be made to the SPARQL query. For example, keep refining your SPARQL query if its result contains irrelevant items or is missing items you expected.
- Do not perform additional computation (e.g. filtering, sorting, calculations) on the result of the SPARQL query to determine the answer. All computation should be done solely within SPARQL.
- For questions with a "True" or "False" answer the SPARQL query should be an ASK query.

[User] when the atlanta braves won the world series?

[Assistant]
To determine when the Atlanta Braves won the World Series, I need to find the years in which the Atlanta Braves, a Major League Baseball team, won the World Series. This information is typically stored in Wikidata as awards or achievements associated with the team.

### Step 1: Identify the entity for the Atlanta Braves
I will first search for the entity representing the Atlanta Braves in Wikidata.

Question: Atlanta Braves

Top 10 entity alternatives:
1. Atlanta Braves (wd:Q461595), also known as Beaneaters, Bees, Boston Beaneaters, Boston Bees, Boston Braves, etc.: Major League Baseball team in Cumberland, Georgia / is instance of baseball team
2. WikiProject Atlanta Braves (wd:Q21829422): Wikimedia subject-area collaboration / is instance of WikiProject
3. history of the Atlanta Braves (wd:Q5869099, matched via Atlanta Braves history), also known as Atlanta Braves history, the Atlanta Braves history: is instance of aspect of history / aspect of history
4. Truist Park (wd:Q17003430, matched via New Atlanta Braves stadium), also known as New Atlanta Braves stadium, Sun Trust Park, SunTrust Park: baseball park in Atlanta metropolitan area / is instance of baseball venue
5. 2017 Atlanta Braves season (wd:Q28035215): is instance of baseball team season / Major League Baseball season
6. 2018 Atlanta Braves season (wd:Q43082437): is instance of baseball team season / Major League Baseball season
7. 2024 Atlanta Braves season (wd:Q123050691): is instance of baseball team season / major League Baseball season
8. 2023 Atlanta Braves season (wd:Q115825396): is instance of baseball team season / major League Baseball season
9. 2022 Atlanta Braves season (wd:Q109311700): is instance of baseball team season / Major League Baseball season
10. 2021 Atlanta Braves season (wd:Q104864718): is instance of baseball team season / Major League Baseball season

[Assistant]
The correct entity for the Atlanta Braves is `wd:Q461595`, which is identified as a Major League Baseball team. Now, I need to find out when they won the World Series. This information would likely be stored as an award or achievement associated with the team.

### Step 2: Search for properties related to awards or championships
I will search for properties related to awards or championships that might be associated with the Atlanta Braves.

Question: award

Top 10 property alternatives:
1. award received (wd:P166 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn, matched via award), also known as award, awarded, awards, awards received, award won, etc.: award or recognition received by a person, organisation or creative work / award or recognition received by a person, organization or creative work / award or recognition received by a person, organization or creative work / awards received by a person, organisation or creative work
2. grants (wd:P5460 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn, matched via awards), also known as awards, bestows, confers, gives out, P5460: confers degree, honor, award, prize, title, certificate or medal denoting achievement to a person or organization
3. winner (wd:P1346 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn, matched via awardee), also known as 1st place medalist, awardee, champ, champion, has winner, etc.: winner of a competition or similar event, not to be used for ... qualified with "for work" (P1686)) or for wars or battles / winner of an event - do not use for awards (use P166 instead), nor for wars or battles / is subproperty of participating team / is subproperty of participant
4. trophy awarded (wd:P4622 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn, matched via cup awarded), also known as cup awarded, diploma awarded, medal awarded, P4622: trophy awarded at the end of a selection process or of a ... or finishers under the form of a cup, a medal, a diploma
5. nominee (wd:P2453 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn, matched via award nominee), also known as award nominee, P2453: qualifier used with “nominated for” to specify which person or organization was nominated
6. conferred by (wd:P1027 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn, matched via awarded by), also known as awarded by, bestowed by, by, conceded by, degree awarded by, etc.: person or organisation who awards a prize to or bestows an honour upon a recipient / person or organization who grants an award, certification, grant, or role
7. nominated for (wd:P1411 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn, matched via selected for award), also known as finalist for, finalist for award, have nomination to, nominated for award, nomination received, etc.: award nomination received by a person, organisation or creative work (inspired from "award received" (Property:P166)) / award nomination received by a person, organisation or creative work (inspired from "award received" (Property:P166))
8. award rationale (wd:P6208 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn, matched via award reason), also known as award citation, award reason, rationale, P6208: qualifier to add short citation explaining the official ... add comments about a person's award. No quote marked needed.
9. together with (wd:P1706 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn, matched via award shared with), also known as accompanied by, alongside, award shared with, feat., featuring, etc.: qualifier to specify the item that this property is shared with
10. inscription (wd:P1684 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn), also known as epigraph (inscription), inscriptions, legend, legenda, signature, etc.: inscriptions, markings and signatures on an object / inscriptions, markings and signatures on an object / inscriptions, markings and signatures on an object

[Assistant]
The most relevant property for awards received is `wdt:P166` (award received). I will now check if the Atlanta Braves (`wd:Q461595`) have any awards associated with them, specifically World Series championships.

### Step 3: Query for awards received by the Atlanta Braves
I will execute a SPARQL query to find the awards received by the Atlanta Braves, focusing on the World Series championships.

execute

SELECT ?award WHERE { wd:Q461595 wdt:P166 ?award }

[Assistant]
The query returned no results, which suggests that the Atlanta Braves' World Series wins are not directly linked via `wdt:P166` (award received). This is not uncommon for sports teams, as championships are often recorded through other means, such as participation in events or through qualifiers like "winner of a competition."

### Step 4: Search for properties related to winning or championships
I will now search for properties related to winning or being a champion in a competition, such as `wdt:P1346` (winner), which is often used for sports teams.

Question: winner

Top 10 property alternatives:
1. winner (wd:P1346 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn), also known as 1st place medalist, awardee, champ, champion, has winner, etc.: winner of a competition or similar event, not to be used for ... qualified with "for work" (P1686)) or for wars or battles / winner of an event - do not use for awards (use P166 instead), nor for wars or battles / is subproperty of participating team / is subproperty of participant
2. number of wins (wd:P1355 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn, matched via won), also known as games won, matches won, match victories, sporting wins, victories, etc.: number of sporting matches, games or events won
3. competition won (wd:P2522 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn, matched via won), also known as victory, winner of, won, won event, P2522: competition or sports event won by the subject / is subproperty of participant in
4. award received (wd:P166 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn, matched via winner of), also known as award, awarded, awards, awards received, award won, etc.: award or recognition received by a person, organisation or creative work / award or recognition received by a person, organization or creative work / award or recognition received by a person, organization or creative work / awards received by a person, organisation or creative work
5. league or competition (wd:P118 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn, matched via tournament), also known as competition, cup, division, sports league, tournament, etc.: league or competition in which team or player has played, or in which an event occurs / is subproperty of participant in / league in which the team plays / league in which the team plays
6. participant (wd:P710 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn, matched via player), also known as accused, agent, attendee, belligerents, between, etc.: person, group of people or organization (object) that ... has role" (P3831). Use P1923 for participants that are teams. / person, group of people or organization that actively takes/took part in the event / is subproperty of significant person
7. successful candidate (wd:P991 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn, matched via winner of election), also known as elected, elected candidate, elected person, election winner, election won by, etc.: person(s) or political organization(s) elected after the election / is subproperty of candidate / is subproperty of winner
8. member of sports team (wd:P54 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn, matched via team), also known as club played for, member of team, of team, part of team, played for, etc.: sports teams or clubs that the subject currently represents or formerly represented / sports teams or clubs that the subject currently represents or formerly represented / sports teams or clubs that the subject represents or represented / is subproperty of member of
9. ranking (wd:P1352 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn), also known as peak position, place, placing, position, rank, etc.: subject's ordinal position as qualitatively evaluated relative to other members of a group / the subject's position in the specified rank
10. reward (wd:P4444 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn), also known as P4444: reward, bonus, or prize received as part of a membership or loyalty program

[Assistant]
The property `wdt:P1346` (winner) is relevant for identifying the winner of a competition. However, for sports teams, it is more common to use `wdt:P2522` (competition won), which directly links a team to the competition they won. I will now check if the Atlanta Braves have won any competitions using `wdt:P2522`.

### Step 5: Query for competitions won by the Atlanta Braves
I will execute a SPARQL query to find the competitions won by the Atlanta Braves using `wdt:P2522`.

SELECT ?competition WHERE { wd:Q461595 wdt:P2522 ?competition }

[Assistant]
The query returned no results, which suggests that the Atlanta Braves' World Series wins are not directly linked via `wdt:P2522` either. This could mean that the World Series wins are recorded as part of the team's season records or through other indirect means.

### Step 6: Explore the team's seasons and their achievements
Since direct links to World Series wins are not found, I will explore the team's seasons (e.g., `2021 Atlanta Braves season`, `1995 Atlanta Braves season`, etc.) to see if any of them have a property indicating a World Series win. I will first look at the seasons associated with the Atlanta Braves.

I will search for entities related to "Atlanta Braves season" to find relevant season items.

Question: Atlanta Braves season

Top 10 entity alternatives:
1. 2017 Atlanta Braves season (wd:Q28035215): is instance of baseball team season / Major League Baseball season
2. 2018 Atlanta Braves season (wd:Q43082437): is instance of baseball team season / Major League Baseball season
3. 2024 Atlanta Braves season (wd:Q123050691): is instance of baseball team season / major League Baseball season
4. 2023 Atlanta Braves season (wd:Q115825396): is instance of baseball team season / major League Baseball season
5. 2022 Atlanta Braves season (wd:Q109311700): is instance of baseball team season / Major League Baseball season
6. 2021 Atlanta Braves season (wd:Q104864718): is instance of baseball team season / Major League Baseball season
7. 2006 Atlanta Braves season (wd:Q4072119): is instance of baseball team season / Major League Baseball season
8. 2014 Atlanta Braves season (wd:Q15911965): is instance of baseball team season / Major League Baseball season
9. 2009 Atlanta Braves season (wd:Q3466473): is instance of baseball team season / Major League Baseball season
10. 2010 Atlanta Braves season (wd:Q3467949): is instance of baseball team season / Major League Baseball season

[Assistant]
Now I will check the properties of one of the more recent seasons, such as the 2021 Atlanta Braves season (`wd:Q104864718`), to see if it has a property indicating a World Series win. I will list the triples for this entity to explore its properties.

list

wd:Q104864718

Got 36 rows and 3 columns, showing the first 10 rows below:
| subject                                    | property                               | object                                     |
| ------------------------------------------ | -------------------------------------- | ------------------------------------------ |
| 2021 Atlanta Braves season (wd:Q104864718) | instance of (wdt:P31)                  | baseball team season (wd:Q26896697)        |
| 2021 Atlanta Braves season (wd:Q104864718) | country (wdt:P17)                      | United States (wd:Q30)                     |
| 2021 Atlanta Braves season (wd:Q104864718) | Google Knowledge Graph ID (wdtn:P2671) | <http://g.co/kg/g/11qm6vxscl>              |
| 2021 Atlanta Braves season (wd:Q104864718) | Commons category (wdt:P373)            | 2021 Atlanta Braves season                 |
| 2021 Atlanta Braves season (wd:Q104864718) | sport (wdt:P641)                       | baseball (wd:Q5369)                        |
| 2021 Atlanta Braves season (wd:Q104864718) | follows (wdt:P155)                     | 2020 Atlanta Braves season (wd:Q73927645)  |
| 2021 Atlanta Braves season (wd:Q104864718) | followed by (wdt:P156)                 | 2022 Atlanta Braves season (wd:Q109311700) |
| 2021 Atlanta Braves season (wd:Q104864718) | point in time (wdt:P585)               | 2021-01-01T00:00:00Z (xsd:dateTime)        |
| 2021 Atlanta Braves season (wd:Q104864718) | season of club or team (wdt:P5138)     | Atlanta Braves (wd:Q461595)                |
| 2021 Atlanta Braves season (wd:Q104864718) | schema:description                     | Major League Baseball season (lang:en)     |
| ...                                        | ...                                    | ...                                        |

[Assistant]
The triples for the 2021 Atlanta Braves season do not directly indicate a World Series win. However, I notice that the team participated in the 2021 MLB playoffs, and the World Series is the final championship of the MLB playoffs. I need to check if the 2021 Atlanta Braves season has a property indicating they won the World Series.

I will search for properties related to "championship" or "World Series" in the context of the team's season.

Question: championship

Top 10 property alternatives:
1. sport (wd:P641 as p/wdt), also known as play, plays, sport played, sports, P641: sport that the subject participates or participated in or is associated with / sport or discipline in which the entity participates or belongs to
2. season of club or team (wd:P5138 as p/wdt, matched via sports season of club or team), also known as season of athletics program, season of club, season of team, sports season of club or team, P5138: club or team that played the season
3. point in time (wd:P585 as p/wdt, matched via on), also known as as of, at time, by date, date, during, etc.: date something took place, existed or a statement was true; for providing time use the "refine date" property (P4241) / time and date something took place, existed or a statement was true / time and date something took place, existed or a statement was true / time and date something took place, existed or a statement was true
4. country (wd:P17 as p/wdt), also known as host country, land, sovereign state, state, P17: sovereign state that this item is in (not to be used for human beings) / sovereign state that this item is in (not to be used for human beings) / sovereign state that this item is in (not to be used for human beings) / sovereign state that this item is in (not to be used for human beings) / is subproperty of located in the administrative territorial entity
5. instance of (wd:P31 as p/wdt, matched via is a), also known as example of, has type, is a, is an, is of type, etc.: type to which this subject corresponds/belongs. Different ... and the volcano is a type (instance) of volcanic landform / that class of which this subject is a particular example and ... a subclass of mountain (and an instance of volcanic landform)
6. followed by (wd:P156 as p/wdt, matched via then), also known as comes before, continued as, next, next element, next is, etc.: immediately following item in a series of which the subject ... replaced, e.g. political offices, use "replaced by" (P1366)] / immediately following item in a series of which the subject ... replaced, e.g. political offices, use "replaced by" (P1366)] / immediately following item in a series of which the subject ... replaced, e.g. political offices, use "replaced by" (P1366)]
7. follows (wd:P155 as p/wdt, matched via is after), also known as before was, comes after, is after, preceded by, predecessor, etc.: immediately prior item in a series of which the subject is a ... item, e.g. political offices, use "replaces" (P1365)] / immediately prior item in a series of which the subject is a ... item, e.g. political offices, use "replaces" (P1365)] / immediately prior item in a series of which the subject is a ... item, e.g. political offices, use "replaces" (P1365)] / immediately prior item in a series of which the subject is a ... item, e.g. political offices, use "replaces" (P1365)]
8. Google Knowledge Graph ID (wd:P2671 as p/wdt/wdtn, matched via kgmid), also known as Google knowledge panel, Google Knowledge Panel ID, kgmid, MREID, P2671: identifier for Google Knowledge Graph API, starting with "/g/". For IDs starting with "/m/", use Freebase ID (P646) / identifier for Google Knowledge Graph API / identifier for Google Knowledge Graph API
9. Commons category (wd:P373 as p/wdt, matched via P373), also known as category Commons, category on Commons, category on Wikimedia Commons, category Wikipedia Commons, commonscat, etc.: name of the Wikimedia Commons category containing files related to this item (without the prefix "Category:") / name of the Wikimedia Commons category containing files related to this item (without the prefix "Category") / name of the Wikimedia Commons category containing files related to this item (without the prefix "Category")

No other items found

[Assistant]
The search for "championship" properties did not yield any relevant results. Let me now search for properties related to "World Series" specifically to see if there is a direct link or if the World Series is represented as a competition in Wikidata.

### Step 7: Search for the World Series entity
I will search for the entity representing the "World Series" in Wikidata.

Question: World Series

Top 10 entity alternatives:
1. World Series (wd:Q265538), also known as Fall Classic: Championship of Major League Baseball / is instance of baseball competition / is instance of tournament
2. World Series (wd:Q23945626): painting by Arnold Friedman / painting by Arnold Friedman / is instance of painting
3. ATP World Tour 250 series (wd:Q300017, matched via ATP World Series), also known as ATP 250, ATP 250 Series, ATP Tour 250, ATP World Series, ATP World Tour 250, etc.: is instance of tennis tour with multiple editions / is subclass of tennis tour / tennis tournament category / tennis tournament / tennis tournament
4. Glory (wd:Q892206, matched via Glory World Series), also known as GLORY, Glory Kickboxing, Glory World Series: is instance of kickboxing organization / world-wide kickboxing promotion / is instance of business
5. 2004 World Series (wd:Q1341797): 100th edition of Major League Baseball's championship series / is instance of season
6. 2018 World Series (wd:Q56692089): 114th edition of Major League Baseball's championship series / is instance of sports competition
7. 2009 World Series (wd:Q155391): 105th edition of Major League Baseball's championship series / is instance of season
8. 2001 World Series (wd:Q1207242), also known as 2001 Major League Baseball World Series: 97th edition of Major League Baseball's championship series / is instance of season
9. 2016 World Series (wd:Q24906838): 112th edition of Major League Baseball's championship series / is instance of sports competition
10. 2002 World Series (wd:Q1187726): 98th edition of Major League Baseball's championship series / is instance of season

[Assistant]
The World Series is represented as `wd:Q265538`, and individual editions (e.g., 2021 World Series) are also listed as separate entities. I will now check if the 2021 Atlanta Braves season (`wd:Q104864718`) is linked to the 2021 World Series (`wd:Q56692089`), or if the Atlanta Braves are listed as the winner of the World Series in any of these editions.

### Step 8: Check if the Atlanta Braves are linked to any World Series edition as the winner
I will search for the winner of the 2021 World Series (`wd:Q56692089`) to see if the Atlanta Braves are listed as the winner.

execute

SELECT ?winner WHERE { wd:Q56692089 wdt:P1346 ?winner }

[Assistant]
It seems there is an error in the data: the Boston Red Sox won the 2018 World Series (`wd:Q56692089`), not the 2021 World Series. The 2021 World Series is actually `wd:Q104864718`'s corresponding World Series, which should be `wd:Q104864718`'s associated competition. Let me find the correct World Series entity for 2021.

### Step 9: Find the correct World Series entity for 2021
I will search for the 2021 World Series entity.

Question: 2021 World Series

Top 10 entity alternatives:
1. 2021 World Series (wd:Q108864102): 117th edition of Major League Baseball's championship series / is instance of sports competition
2. WUFA World Series 2021 (wd:Q106939015): international football competition / is instance of season
3. 2021 College World Series (wd:Q106900771): Final stage of the 2021 NCAA Division I Baseball Tournament / is instance of season
4. 2021 ITU World Triathlon Series (wd:Q60969210), also known as 2021 World Triathlon Championship Series: is instance of season / sports season
5. 2021 World Series of Poker (wd:Q106419732): is instance of poker tournament series / Series of poker tournaments
6. 2021 World Rugby Sevens Series (wd:Q107471680): 22nd annual international series of tournaments in men's rugby sevens / is instance of season
7. 2021 World Series of Darts (wd:Q106624712): is instance of season / darts tournament
8. 2021 Little League World Series (wd:Q107298742): American baseball competition / is instance of season
9. Golden Trail World Series 2021 (wd:Q106145911): is instance of season
10. 2021 Pacific Four Series (wd:Q111908954, matched via World Rugby Pacific Four Series 2021), also known as World Rugby Pacific Four Series 2021: 1st edition of women's rugby union Pacific Four Series / is instance of season

[Assistant]
The correct entity for the 2021 World Series is `wd:Q108864102`. Now, I will check who won the 2021 World Series by querying the winner property (`wdt:P1346`) for this entity.

SELECT ?winner WHERE { wd:Q108864102 wdt:P1346 ?winner }

[Assistant]
Great! The query confirms that the Atlanta Braves won the 2021 World Series. Now, I need to find all the years in which the Atlanta Braves won the World Series. To do this, I will find all World Series editions where the Atlanta Braves are listed as the winner.

### Step 10: Find all World Series wins by the Atlanta Braves
I will execute a SPARQL query to find all World Series editions where the Atlanta Braves (`wd:Q461595`) are the winner (`wdt:P1346`).

SELECT ?worldSeries WHERE { ?worldSeries wdt:P1346 wd:Q461595 }

Got 13 rows and 1 column, showing the first 5 and last 5 rows below:
| worldSeries                                              |
| -------------------------------------------------------- |
| 1999 National League Championship Series (wd:Q1001848)   |
| 1996 National League Championship Series (wd:Q1004378)   |
| 2021 Major League Baseball season (wd:Q104804976)        |
| 2021 National League Championship Series (wd:Q108857031) |
| 2021 World Series (wd:Q108864102)                        |
| ...                                                      |
| 1991 National League Championship Series (wd:Q3511245)   |
| 1992 National League Championship Series (wd:Q3511246)   |
| 1957 Major League Baseball season (wd:Q4569021)          |
| 1995 World Series (wd:Q636375)                           |
| 1957 World Series (wd:Q987878)                           |

[Assistant]
The results include both World Series and National League Championship Series (NLCS) wins. The Atlanta Braves won the NLCS multiple times but only won the World Series in 1957, 1995, and 2021. I need to filter for only the World Series events.

### Step 11: Filter for only World Series events
I will modify the query to ensure that only entities that are instances of "World Series" (`wd:Q265538`) are returned.

SELECT ?worldSeries WHERE { ?worldSeries wdt:P1346 wd:Q461595 ; wdt:P31 wd:Q265538 }

[Assistant]
The query returned no results, which suggests that the World Series entities may not have `wdt:P31 wd:Q265538` directly attached. Instead, the World Series entities might be instances of "sports competition" or another more general class. Let me check the instance-of (`wdt:P31`) of one of the World Series entities returned earlier, such as `wd:Q108864102` (2021 World Series), to see its type.

list

wd:Q108864102

[Assistant]
The 2021 World Series is an instance of `wd:Q13406554` (sports competition), not `wd:Q265538` (World Series). This suggests that `wd:Q265538` is not used as a direct instance-of for individual World Series editions. Instead, the World Series is a general concept, and each edition is a sports competition.

To find all World Series wins by the Atlanta Braves, I will need to rely on the fact that the World Series is a baseball competition (`wdt:P641 wd:Q5369`) and that the winner is linked via `wdt:P1346`. I will modify the query to filter for baseball competitions.

### Step 12: Filter for baseball World Series wins
I will execute a query to find all sports competitions that are baseball competitions (`wdt:P641 wd:Q5369`) and where the Atlanta Braves are the winner (`wdt:P1346 wd:Q461595`).

execute

SELECT ?worldSeries WHERE { ?worldSeries wdt:P1346 wd:Q461595 ; wdt:P641 wd:Q5369 }

Got 13 rows and 1 column, showing the first 5 and last 5 rows below:
| worldSeries                                              |
| -------------------------------------------------------- |
| 1999 National League Championship Series (wd:Q1001848)   |
| 1996 National League Championship Series (wd:Q1004378)   |
| 2021 Major League Baseball season (wd:Q104804976)        |
| 2021 National League Championship Series (wd:Q108857031) |
| 2021 World Series (wd:Q108864102)                        |
| ...                                                      |
| 1991 National League Championship Series (wd:Q3511245)   |
| 1992 National League Championship Series (wd:Q3511246)   |
| 1957 Major League Baseball season (wd:Q4569021)          |
| 1995 World Series (wd:Q636375)                           |
| 1957 World Series (wd:Q987878)                           |

[Assistant]
The results still include National League Championship Series (NLCS) and general season entries. I need to refine the query further to distinguish between the World Series and other baseball competitions.

Looking at the data, the World Series entities have labels like "2021 World Series" and are distinct from NLCS. I can use the label to filter for entities whose label contains "World Series". I will use a `FILTER` on the label to extract only those entities.

### Step 13: Filter by label containing "World Series"
I will modify the query to include a filter on the English label of the competition to ensure it contains "World Series".

SELECT ?worldSeries WHERE { ?worldSeries wdt:P1346 wd:Q461595 ; wdt:P641 wd:Q5369 . ?worldSeries rdfs:label ?label . FILTER(LANG(?label) = "en") . FILTER(CONTAINS(LCASE(?label), "world series")) }

[Assistant]
Perfect! The query now correctly returns the three World Series wins by the Atlanta Braves: **1957**, **1995**, and **2021**.

### Final Answer
The Atlanta Braves won the World Series in the following years: **1957**, **1995**, and **2021**.

I will now provide the final SPARQL query and answer.

answer

SELECT ?worldSeries WHERE { ?worldSeries wdt:P1346 wd:Q461595 ; wdt:P641 wd:Q5369 . ?worldSeries rdfs:label ?label . FILTER(LANG(?label) = "en") . FILTER(CONTAINS(LCASE(?label), "world series")) }

Answer: The Atlanta Braves won the World Series in 1957, 1995, and 2021.


PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX wdt: <http://www.wikidata.org/prop/direct/>
PREFIX wd: <http://www.wikidata.org/entity/>
SELECT ?label ?breed ?country ?height ?mass WHERE {
  wd:Q39285 rdfs:label ?label .
  FILTER ( LANG( ?label ) = "en" ) .
  wd:Q39285 wdt:P31 ?breed .
  wd:Q39285 wdt:P495 ?country .
  wd:Q39285 wdt:P2048 ?height .
  wd:Q39285 wdt:P2067 ?mass .
  ?breed rdfs:label ?breedLabel .
  FILTER ( LANG( ?breedLabel ) = "en" ) .
  ?country rdfs:label ?countryLabel .
  FILTER ( LANG( ?countryLabel ) = "en" )
}

Using entities:
- Staffordshire Bull Terrier (wd:Q39285), also known as Staffbull, Staffie: is instance of dog breed / is subclass of dog / is subclass of terrier / dog breed

Using properties:
- height (wd:P2048 as wdt), also known as depth over terrain, heighth, size, P2048: is subproperty of length / vertical dimension of an entity / vertical length of an entity
- mass (wd:P2067 as wdt), also known as displacement, molecular mass, molecular weight, weight, P2067: mass (in colloquial usage also known as weight) of the item / mass (in colloquial usage also known as weight) of the item / mass (in colloquial usage also known as weight) of the item / mass (in colloquial usage also known as weight) of the item
- instance of (wd:P31 as wdt), also known as example of, has type, is a, is an, is of type, etc.: that class of which this subject is a particular example and ... a subclass of mountain (and an instance of volcanic landform) / type to which this subject corresponds/belongs. Different ... and the volcano is a type (instance) of volcanic landform
- country of origin (wd:P495 as wdt), also known as comes from, CoO, country, originates from, origin country, etc.: is subproperty of country / is subproperty of significant place / country of origin of this item (creative work, food, phrase, product, etc.) / country of origin of this item (creative work, food, phrase, product, etc.) / country of origin of this item (creative work, food, phrase, product, etc.)

Got 8 rows and 5 columns:
| label                                | breed                 | country          | height             | mass               |
| ------------------------------------ | --------------------- | ---------------- | ------------------ | ------------------ |
| Staffordshire Bull Terrier (lang:en) | dog breed (wd:Q39367) | England (wd:Q21) | 35.5 (xsd:decimal) | 11 (xsd:decimal)   |
| Staffordshire Bull Terrier (lang:en) | dog breed (wd:Q39367) | England (wd:Q21) | 40.5 (xsd:decimal) | 11 (xsd:decimal)   |
| Staffordshire Bull Terrier (lang:en) | dog breed (wd:Q39367) | England (wd:Q21) | 35.5 (xsd:decimal) | 12.7 (xsd:decimal) |
| Staffordshire Bull Terrier (lang:en) | dog breed (wd:Q39367) | England (wd:Q21) | 40.5 (xsd:decimal) | 12.7 (xsd:decimal) |
| Staffordshire Bull Terrier (lang:en) | dog breed (wd:Q39367) | England (wd:Q21) | 35.5 (xsd:decimal) | 15.4 (xsd:decimal) |
| Staffordshire Bull Terrier (lang:en) | dog breed (wd:Q39367) | England (wd:Q21) | 40.5 (xsd:decimal) | 15.4 (xsd:decimal) |
| Staffordshire Bull Terrier (lang:en) | dog breed (wd:Q39367) | England (wd:Q21) | 35.5 (xsd:decimal) | 17 (xsd:decimal)   |
| Staffordshire Bull Terrier (lang:en) | dog breed (wd:Q39367) | England (wd:Q21) | 40.5 (xsd:decimal) | 17 (xsd:decimal)   |

Answer: Staffordshire terriers commonly refer to the Staffordshire Bull Terrier, a breed of dog originating from England. It is a muscular, compact breed known for its loyalty and affectionate nature. It typically stands between 35.5 cm and 40.5 cm tall and weighs between 11 kg and 17 kg.

Staffordshire terriers commonly refer to the Staffordshire Bull Terrier, a breed of dog originating from England. It is a muscular, compact breed known for its loyalty and affectionate nature. It typically stands between 35.5 cm and 40.5 cm tall and weighs between 11 kg and 17 kg.

SPARQL query over wikidata:
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX wdt: <http://www.wikidata.org/prop/direct/>
PREFIX wd: <http://www.wikidata.org/entity/>
SELECT ?label ?breed ?country ?height ?mass WHERE {
  wd:Q39285 rdfs:label ?label .
  FILTER ( LANG( ?label ) = "en" ) .
  wd:Q39285 wdt:P31 ?breed .
  wd:Q39285 wdt:P495 ?country .
  wd:Q39285 wdt:P2048 ?height .
  wd:Q39285 wdt:P2067 ?mass .
  ?breed rdfs:label ?breedLabel .
  FILTER ( LANG( ?breedLabel ) = "en" ) .
  ?country rdfs:label ?countryLabel .
  FILTER ( LANG( ?countryLabel ) = "en" )
}

Using entities:
- Staffordshire Bull Terrier (wd:Q39285), also known as Staffbull, Staffie: is instance of dog breed / is subclass of dog / is subclass of terrier / dog breed

Using properties:
- height (wd:P2048 as wdt), also known as depth over terrain, heighth, size, P2048: is subproperty of length / vertical dimension of an entity / vertical length of an entity
- mass (wd:P2067 as wdt), also known as displacement, molecular mass, molecular weight, weight, P2067: mass (in colloquial usage also known as weight) of the item / mass (in colloquial usage also known as weight) of the item / mass (in colloquial usage also known as weight) of the item / mass (in colloquial usage also known as weight) of the item
- instance of (wd:P31 as wdt), also known as example of, has type, is a, is an, is of type, etc.: that class of which this subject is a particular example and ... a subclass of mountain (and an instance of volcanic landform) / type to which this subject corresponds/belongs. Different ... and the volcano is a type (instance) of volcanic landform
- country of origin (wd:P495 as wdt), also known as comes from, CoO, country, originates from, origin country, etc.: is subproperty of country / is subproperty of significant place / country of origin of this item (creative work, food, phrase, product, etc.) / country of origin of this item (creative work, food, phrase, product, etc.) / country of origin of this item (creative work, food, phrase, product, etc.)

Execution result:
Got 8 rows and 5 columns:
| label                                | breed                 | country          | height             | mass               |
| ------------------------------------ | --------------------- | ---------------- | ------------------ | ------------------ |
| Staffordshire Bull Terrier (lang:en) | dog breed (wd:Q39367) | England (wd:Q21) | 35.5 (xsd:decimal) | 11 (xsd:decimal)   |
| Staffordshire Bull Terrier (lang:en) | dog breed (wd:Q39367) | England (wd:Q21) | 40.5 (xsd:decimal) | 11 (xsd:decimal)   |
| Staffordshire Bull Terrier (lang:en) | dog breed (wd:Q39367) | England (wd:Q21) | 35.5 (xsd:decimal) | 12.7 (xsd:decimal) |
| Staffordshire Bull Terrier (lang:en) | dog breed (wd:Q39367) | England (wd:Q21) | 40.5 (xsd:decimal) | 12.7 (xsd:decimal) |
| Staffordshire Bull Terrier (lang:en) | dog breed (wd:Q39367) | England (wd:Q21) | 35.5 (xsd:decimal) | 15.4 (xsd:decimal) |
| Staffordshire Bull Terrier (lang:en) | dog breed (wd:Q39367) | England (wd:Q21) | 40.5 (xsd:decimal) | 15.4 (xsd:decimal) |
| Staffordshire Bull Terrier (lang:en) | dog breed (wd:Q39367) | England (wd:Q21) | 35.5 (xsd:decimal) | 17 (xsd:decimal)   |
| Staffordshire Bull Terrier (lang:en) | dog breed (wd:Q39367) | England (wd:Q21) | 40.5 (xsd:decimal) | 17 (xsd:decimal)   |

[System]
You are a question answering assistant. Your job is to generate a SPARQL query to answer a given user question.

You should follow a step-by-step approach to generate the SPARQL query:
1. Determine possible entities and properties implied by the user question.
2. Search for the entities and properties in the knowledge graphs. Where applicable, constrain the searches with already identified entities and properties.
3. Gradually build up the SPARQL query using the identified entities and properties. Start with simple queries and add more complexity as needed. Execute intermediate queries to get feedback and to verify your assumptions. You may need to refine or rethink your current plan based on the query results and go back to step 2 if needed, possibly multiple times.
4. Use the answer or cancel function to finalize your answer and stop the generation process.

Available knowledge graphs:
- wikidata at http://localhost:7001 with prefix index for entities and similarity index for properties, and notes:
  - P106 = occupation. Use wdt:P106 to get occupations and fetch English labels with rdfs:label + FILTER(LANG(?label)="en"). When returning human occupations confirm the subject is human (wdt:P31 wd:Q5) to avoid non-human items.
  - Population (P1082) and tabular (P4179): use wdt:P1082 for quick/direct values; for time-series/point-in-time use p:P1082 + ps:P1082 + pq:P585 and ORDER BY pq:P585 DESC. Inspect statement qualifiers (e.g., 'applies to part') and prov:wasDerivedFrom references (pr:P854 etc.) to detect city-proper vs metro/prefecture scopes before using values.
  - Common person properties: P31 (instance of human Q5), P106 (occupation), P569 (date of birth), P19 (place of birth), P27 (country of citizenship), P21 (sex/gender), P166 (award received). Use wdt: for direct values when possible.
  - P17 (country) can be incomplete/misleading for places (historical/overseas tags). To get modern cities in a country combine: instance-of city (P31=Q515) + wdt:P17 OR use wdt:P131* to find an admin parent whose wdt:P17 = the country. Also cross-check coordinates (P625) or admin hierarchy to spot outliers.
  - When filtering by date of birth (P569) use xsd:dateTime comparisons (e.g. >= "1900-01-01T00:00:00Z"^^xsd:dateTime). Be aware many items have year-only or imprecise dates and coverage is biased toward notable/public figures (sportspeople, politicians, artists).
  - To retrieve qualifiers (e.g., award year) use the statement/qualifier pattern: p:Pxxx / ps:Pxxx / pq:P585. Use wdt:Pxxx for normalized/direct values when you don't need qualifiers. Example: p:P166 + pq:P585 gives award year.
  - To get a person's occupations: use wdt:P106 for direct/normalized values and rdfs:label for human-readable names (FILTER(LANG(...))). Example: wd:Q... wdt:P106 ?occ . ?occ rdfs:label ?occLabel . FILTER(LANG(?occLabel)="en").
  - P166 = award received. Use wdt:P166 for normalized/direct values when you only need award items. To get award years or qualifiers use p:P166 / ps:P166 / pq:P585. Many statements lack pq:P585 — use OPTIONAL { ?stmt pq:P585 ?date } and ORDER BY DESC(?date). When listing award winners, filter ?person wdt:P31 wd:Q5 to ensure humans.
  - Population time-series pattern: wd:Q... p:P1082 ?stmt . ?stmt ps:P1082 ?pop . OPTIONAL { ?stmt pq:P585 ?date } . ORDER BY DESC(?date). pq:P585 is the point-in-time qualifier. IMPORTANT: time-series may mix scopes (city proper vs metro) — e.g., Tokyo has a 2016 entry ~38,140,000 likely metro vs smaller city figures. Inspect qualifiers/references for scope before use.
  - Use wdt:P131* to traverse the admin hierarchy and compare wdt:P17 on the place vs an admin parent to detect historical/colonial country assignments. When mismatches appear, inspect the admin parent's instance-of (P31), labels, qualifiers and references to interpret the historical scope.
  - wdt:P106 often yields multiple occupations for a person. Use GROUP_CONCAT(DISTINCT ?occLabel; separator=", ") or return multiple rows. Always fetch labels with rdfs:label + FILTER(LANG(?label)="en") to get readable occupation names.
  - When a search_entity returns multiple hits (person vs sculpture vs memorial), confirm you selected the human/statements by checking wdt:P31 (instance of) and relevant wdt: properties (e.g., wdt:P106). This avoids using a non-human QID by mistake.
  - search_autocomplete can be constrained with a SPARQL pattern containing ?search (e.g., SELECT * WHERE { ?search wdt:P31 wd:Q5 }). Use constraints to focus results (e.g., humans) and avoid ambiguous fallbacks; if it returns no results, fallback to search_entity and verify wdt:P31.
  - Use search_property_of_entity to find relevant properties for an entity (e.g., 'award' -> P166) and search_object_of_property to discover candidate objects (e.g., 'physicist' for P106). This reduces guessing P/Q ids and surfaces qualifiers.
  - Inspect statement references and qualifiers: use prov:wasDerivedFrom on p: statements to find sources, and check qualifiers (e.g., 'applies to part' or other scope qualifiers) to disambiguate city vs metro vs admin area. Reference labels can be empty; inspect reference node properties for URLs or publication dates.

Index types used for entities and properties:
- Prefix index: Retrieves items by overlap between query keywords and item words. The query keywords can match item words exactly or as prefixes.
- Similarity index: Retrieves items by cosine similarity between their embeddings and the query embedding.

General notes across knowledge graphs:
- Use rdfs:label + FILTER(LANG(?label)="en") for labels; avoid SERVICE wikibase:label. Use wdt:Pxxx for normalized/direct values when qualifiers aren't needed. Use p:Pxxx / ps:Pxxx / pq:Pxxx to access statement qualifiers (e.g., award year via pq:P585). When dates matter, prefer xsd:dateTime and watch for year-only precision.
- Practical query patterns: use rdfs:label + FILTER(LANG(...)) for labels. Use wdt:Pxxx for direct/normalized values when qualifiers aren't needed. Use p:Pxxx / ps:Pxxx / pq:Pxxx to access qualifiers (dates via pq:P585). For dates use xsd:dateTime and expect year-only precision. For places: combine P17 with P131 or coordinate (P625) filters to avoid historical/overseas mismatches.
- Use OPTIONAL for pq: qualifiers (e.g., pq:P585), sort by qualifier (ORDER BY pq:P585 DESC) to prefer recent values. Use GROUP_CONCAT to combine multiple labels/values in one row. Watch for typed literals (xsd:dateTime, xsd:decimal) when filtering or sorting.
- Before querying, use search_entity to resolve human-friendly names to wd:Q identifiers and verify instance-of (e.g., check wdt:P31 = wd:Q5 for humans) to avoid ambiguous matches. Prefer the top match but programmatically confirm P31 before using its data.
- Use search_property to confirm property identifiers (e.g., "country" -> P17) before embedding them in queries. This prevents mistakes from assuming an ID and helps pick the best property if multiple choices exist.
- search_autocomplete can fall back to an unconstrained search or error when there are too many candidates. If this happens (e.g., "more than the maximum supported number of subject candidates"), retry with narrower constraints such as instance-of (wdt:P31), additional type filters, or short prefixes to reduce the candidate set; otherwise fallback to search_entity and verify wdt:P31.
- Use list(...) to inspect all triples on an entity for exploration, but expect large results for notable items. Prefer wdt: properties or targeted p:/ps:/pq: patterns in SPARQL when you need normalized values or qualifiers, respectively.
- Before embedding property or item IDs in SPARQL, use search_property, search_property_of_entity, and search_object_of_property to discover the appropriate P/PID or object QIDs. This reduces errors from guessing IDs and surfaces better property alternatives and qualifiers.
- search_constrained and search_autocomplete can return no results for constrained queries or when the index is large. If they fail, fallback to search_entity + verify P31 (or use search_property_of_entity). Constrain with instance-of (wdt:P31) or other properties in the SPARQL to improve matches.
- When selecting awards by year, prefer xsd:dateTime range filters (e.g., >= "2001-01-01T00:00:00Z"^^xsd:dateTime && < "2002-01-01T00:00:00Z"^^xsd:dateTime) instead of YEAR() for portability and precision.
- When selecting award winners via wdt:P166, filter ?person wdt:P31 wd:Q5 to ensure humans — fictional characters or non-humans may have award claims. If you need award years use p:P166 / ps:P166 / pq:P585 and OPTIONAL { ?stmt pq:P585 ?year } to retrieve qualifier years.
- Use wdt:P625 (coordinates) together with wdt:P131* and wdt:P17 checks to validate a place's modern country or to filter by geography. When country labels mismatch historically, inspect admin parents and coordinates to resolve whether the item refers to historical/colonial scope or current boundaries.
- Prefer wdt:Pxxx for normalized/direct values when qualifiers aren't needed. Use p:Pxxx / ps:Pxxx / pq:Pxxx to access qualifiers (e.g., pq:P585 for award year). Always fetch labels with rdfs:label + FILTER(LANG(?label) = "en").
- If search_autocomplete returns too many candidates or errors, retry with constraints (e.g., SELECT * WHERE { ?search wdt:P31 wd:Q5 }) or narrower query text. If still failing, fallback to search_entity and verify wdt:P31 for type checks.
- For award-year queries use p:P166 / ps:P166 / pq:P585 to access award statements and year qualifiers. Filter by xsd:dateTime ranges (e.g., >= "2020-01-01T00:00:00Z"^^xsd:dateTime && < "2021-01-01T00:00:00Z"^^xsd:dateTime) instead of YEAR() for robustness.
- Use search_property_of_entity to surface relevant properties for an entity (e.g., 'birth' -> P569/P19). list(...) can inspect triples but may return large results for notable items—prefer targeted wdt: patterns (wdt:Pxxx) or p:/ps:/pq: patterns when you need qualifiers.

SPARQL prefixes for use in function calls:
- bd: <http://www.bigdata.com/rdf#
- cc: <http://creativecommons.org/ns#
- data: <https://www.wikidata.org/wiki/Special:EntityData/
- dc: <http://purl.org/dc/elements/1.1/
- dct: <http://purl.org/dc/terms/
- foaf: <http://xmlns.com/foaf/0.1/
- geo: <http://www.opengis.net/ont/geosparql#
- geof: <http://www.opengis.net/def/function/geosparql/
- gn: <http://www.geonames.org/ontology#
- hint: <http://www.bigdata.com/queryHints#
- imdb: <https://www.imdb.com/
- math: <http://www.w3.org/2005/xpath-functions/math#
- ontolex: <http://www.w3.org/ns/lemon/ontolex#
- owl: <http://www.w3.org/2002/07/owl#
- p: <http://www.wikidata.org/prop/
- pq: <http://www.wikidata.org/prop/qualifier/
- pqn: <http://www.wikidata.org/prop/qualifier/value-normalized/
- pqv: <http://www.wikidata.org/prop/qualifier/value/
- pr: <http://www.wikidata.org/prop/reference/
- prn: <http://www.wikidata.org/prop/reference/value-normalized/
- prov: <http://www.w3.org/ns/prov#
- prv: <http://www.wikidata.org/prop/reference/value/
- ps: <http://www.wikidata.org/prop/statement/
- psn: <http://www.wikidata.org/prop/statement/value-normalized/
- psv: <http://www.wikidata.org/prop/statement/value/
- qb: <http://purl.org/linked-data/cube#
- qfn: <http://qlever.cs.uni-freiburg.de/function#
- ql: <http://qlever.cs.uni-freiburg.de/builtin-functions/
- qlss: <https://qlever.cs.uni-freiburg.de/spatialSearch/
- rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#
- rdfs: <http://www.w3.org/2000/01/rdf-schema#
- ref: <http://www.wikidata.org/reference/
- s: <http://www.wikidata.org/entity/statement/
- schema: <http://schema.org/
- skos: <http://www.w3.org/2004/02/skos/core#
- v: <http://www.wikidata.org/value/
- void: <http://rdfs.org/ns/void#
- wd: <http://www.wikidata.org/entity/
- wdno: <http://www.wikidata.org/prop/novalue/
- wdt: <http://www.wikidata.org/prop/direct/
- wdtn: <http://www.wikidata.org/prop/direct-normalized/
- wikibase: <http://wikiba.se/ontology#
- xsd: <http://www.w3.org/2001/XMLSchema#

Additional rules to follow:
- Explain your thought process before and after each step and function call.
- Do not just use or make up entity or property identifiers without verifying their existence in the knowledge graphs first.
- Do not ask the user for clarifications without first attempting to complete the task. If the task input is incomplete or ambiguous, try to make reasonable assumptions and document them.
- Do not use "SERVICE wikibase:label { bd:serviceParam wikibase:language ..." in SPARQL queries. It is not SPARQL standard and unsupported by the used QLever SPARQL endpoints. Use rdfs:label or similar properties to get labels instead.
- Always execute your final SPARQL query before giving an answer to make sure it returns the expected results.
- The SPARQL query should always return the actual identifiers / IRIs of the items in its result. It additionally may return labels or other human-readable information, but they are optional and should be put within optional clauses unless explicitly requested by the user.
- Do not stop early if there are still obvious improvements to be made to the SPARQL query. For example, keep refining your SPARQL query if its result contains irrelevant items or is missing items you expected.
- Do not perform additional computation (e.g. filtering, sorting, calculations) on the result of the SPARQL query to determine the answer. All computation should be done solely within SPARQL.
- For questions with a "True" or "False" answer the SPARQL query should be an ASK query.

[User] what are staffordshire terriers?

[Assistant]
To answer the question "What are Staffordshire terriers?", I need to find information about Staffordshire terriers, which are a breed of dog. I'll start by searching for the entity "Staffordshire terrier" in Wikidata to identify its correct identifier and understand its properties.

Question: Staffordshire terrier

Top 10 entity alternatives:
1. American Staffordshire Terrier (wd:Q37688), also known as AmStaff, AST: is instance of dog breed / is subclass of dog / dog breed
2. Staffordshire Bull Terrier (wd:Q39285), also known as Staffbull, Staffie: is instance of dog breed / is subclass of terrier / is subclass of dog / dog breed
3. Irish Staffordshire Bull Terrier (wd:Q21170233), also known as Irish Bull Terrier: is instance of dog breed / dog breed
4. Myotonia in a Staffordshire terrier (wd:Q71829041): scientific article published on 01 July 1983 / is instance of scholarly article / is instance of academic article
5. Wolverhampton (wd:Q126269, matched via Wolverhampton, Staffordshire), also known as Wolverhampton, England, Wolverhampton, Staffordshire, Wolverhampton, United Kingdom, Wolverhampton, West Midlands: city in the West Midlands, England, United Kingdom / is instance of city
6. Staffordshire (wd:Q23105), also known as Staffs: is instance of Ceremonial counties of England / is instance of ceremonial county of England / ceremonial county in England / ceremonial county in England / ceremonial county of England
7. Lichfield (wd:Q207371, matched via Lichfield, Staffordshire), also known as Leitocaiton, Lichfield, Staffordshire: cathedral city in Staffordshire, England / is instance of civil parish / is instance of city
8. Berti Vogts (wd:Q828203, matched via Terrier), also known as Hans-Hubert "Berti" Vogts, Hans Hubert Vogts, Hans-Hubert Vogts, Terrier, Vogts, Hans-Hubert: has occupation association football manager / has occupation association football player / German footballer and manager / has occupation soccer player / has occupation soccer coach / is instance of human
9. Stafford (wd:Q826782, matched via Stafford, Staffordshire), also known as Stafford, Staffordshire: county town of Staffordshire in the West Midlands, England / is instance of unparished area / is instance of county town
10. terrier (wd:Q38984), also known as Terriers: is subclass of hunting dog / is instance of dog type / dog type

[Assistant]
The search results show that "Staffordshire terrier" most likely refers to either the **American Staffordshire Terrier** (wd:Q37688) or the **Staffordshire Bull Terrier** (wd:Q39285), both of which are recognized dog breeds. The term "Staffordshire terrier" is often used informally to refer to the Staffordshire Bull Terrier, which is a specific breed originating from Staffordshire, England.

To clarify, I will now investigate the **Staffordshire Bull Terrier** (wd:Q39285), as it is the most commonly referenced breed under this name, and check its properties to provide a detailed description.

I'll list the triples for this entity to understand its classification and characteristics.

list

wd:Q39285

Got 227 rows and 3 columns, showing the first 10 rows below:
| subject                                | property                     | object                                                           |
| -------------------------------------- | ---------------------------- | ---------------------------------------------------------------- |
| Staffordshire Bull Terrier (wd:Q39285) | instance of (wdt:P31)        | dog breed (wd:Q39367)                                            |
| Staffordshire Bull Terrier (wd:Q39285) | catalog code (wdt:P528)      | 076                                                              |
| Staffordshire Bull Terrier (wd:Q39285) | Commons category (wdt:P373)  | Staffordshire Bull Terrier                                       |
| Staffordshire Bull Terrier (wd:Q39285) | image (wdt:P18)              | <http://commons.wikimedia.org/wiki/Special:FilePath/Staffie.jpg> |
| Staffordshire Bull Terrier (wd:Q39285) | subclass of (wdt:P279)       | dog (wd:Q144)                                                    |
| Staffordshire Bull Terrier (wd:Q39285) | Freebase ID (wdt:P646)       | /m/01kv93                                                        |
| Staffordshire Bull Terrier (wd:Q39285) | country of origin (wdt:P495) | England (wd:Q21)                                                 |
| Staffordshire Bull Terrier (wd:Q39285) | mass (wdt:P2067)             | 11 (xsd:decimal)                                                 |
| Staffordshire Bull Terrier (wd:Q39285) | height (wdt:P2048)           | 35.5 (xsd:decimal)                                               |
| Staffordshire Bull Terrier (wd:Q39285) | different from (wdt:P1889)   | Bull Terrier (wd:Q38322)                                         |
| ...                                    | ...                          | ...                                                              |

[Assistant]
From the triples, I can see that the **Staffordshire Bull Terrier** (wd:Q39285) is classified as a **dog breed** and is a subclass of **dog**. It originates from **England** and has specific physical characteristics such as a mass of approximately 11 kg and a height of about 35.5 cm.

Now, I will check for additional descriptive information, such as its English label and any other relevant properties like "description" or "breed standard" to provide a comprehensive answer. I'll also check if there is a description property (P1813) for a textual definition.

wd:Q39285

Got 40 rows and 3 columns, showing the first 10 rows below:
| subject                                | property   | object                               |
| -------------------------------------- | ---------- | ------------------------------------ |
| Staffordshire Bull Terrier (wd:Q39285) | rdfs:label | bulterier Staffordshire (lang:ms)    |
| Staffordshire Bull Terrier (wd:Q39285) | rdfs:label | Chó sục Bun Staffordshire (lang:vi)  |
| Staffordshire Bull Terrier (wd:Q39285) | rdfs:label | Daeargi Tarw Stafford (lang:cy)      |
| Staffordshire Bull Terrier (wd:Q39285) | rdfs:label | Staffordshire Bull Tarrie (lang:sco) |
| Staffordshire Bull Terrier (wd:Q39285) | rdfs:label | staffordshire bullterrier (lang:hu)  |
| Staffordshire Bull Terrier (wd:Q39285) | rdfs:label | Staffordshire bull terrier (lang:es) |
| Staffordshire Bull Terrier (wd:Q39285) | rdfs:label | Staffordshire bull terrier (lang:eu) |
| Staffordshire Bull Terrier (wd:Q39285) | rdfs:label | Staffordshire bull terrier (lang:lv) |
| Staffordshire Bull Terrier (wd:Q39285) | rdfs:label | Staffordshire bull terrier (lang:nb) |
| Staffordshire Bull Terrier (wd:Q39285) | rdfs:label | Staffordshire bull terrier (lang:nn) |
| ...                                    | ...        | ...                                  |

[Assistant]
I see that the English label for the entity is "Staffordshire bull terrier" (lowercase in the data, but standard capitalization is "Staffordshire Bull Terrier"). Now, I'll check for a description (P1813) in English to get a concise definition.

wd:Q39285

[Assistant]
It seems there is no direct description (P1813) available in Wikidata for the Staffordshire Bull Terrier. However, based on the information gathered so far, I can construct a clear and accurate answer.

The **Staffordshire Bull Terrier** is a breed of dog originating from England. It is classified as a dog breed (wd:Q39367) and is a subclass of the dog (wd:Q144). It is known for its compact, muscular build, with an average height of about 35.5 cm and a mass of approximately 11 kg. It is distinct from other breeds like the Bull Terrier and the American Staffordshire Terrier.

To provide a complete and structured answer, I will now write a SPARQL query that retrieves the key properties of the Staffordshire Bull Terrier (wd:Q39285), including its label, classification, country of origin, height, and mass, in English. This will allow me to confirm the details before finalizing the answer.

execute

SELECT ?label ?breed ?country ?height ?mass WHERE { wd:Q39285 rdfs:label ?label . FILTER(LANG(?label) = "en") . wd:Q39285 wdt:P31 ?breed . wd:Q39285 wdt:P495 ?country . wd:Q39285 wdt:P2048 ?height . wd:Q39285 wdt:P2067 ?mass . ?breed rdfs:label ?breedLabel . FILTER(LANG(?breedLabel) = "en") . ?country rdfs:label ?countryLabel . FILTER(LANG(?countryLabel) = "en") }

Got 8 rows and 5 columns:
| label                                | breed                 | country          | height             | mass               |
| ------------------------------------ | --------------------- | ---------------- | ------------------ | ------------------ |
| Staffordshire Bull Terrier (lang:en) | dog breed (wd:Q39367) | England (wd:Q21) | 35.5 (xsd:decimal) | 11 (xsd:decimal)   |
| Staffordshire Bull Terrier (lang:en) | dog breed (wd:Q39367) | England (wd:Q21) | 35.5 (xsd:decimal) | 12.7 (xsd:decimal) |
| Staffordshire Bull Terrier (lang:en) | dog breed (wd:Q39367) | England (wd:Q21) | 35.5 (xsd:decimal) | 15.4 (xsd:decimal) |
| Staffordshire Bull Terrier (lang:en) | dog breed (wd:Q39367) | England (wd:Q21) | 35.5 (xsd:decimal) | 17 (xsd:decimal)   |
| Staffordshire Bull Terrier (lang:en) | dog breed (wd:Q39367) | England (wd:Q21) | 40.5 (xsd:decimal) | 11 (xsd:decimal)   |
| Staffordshire Bull Terrier (lang:en) | dog breed (wd:Q39367) | England (wd:Q21) | 40.5 (xsd:decimal) | 12.7 (xsd:decimal) |
| Staffordshire Bull Terrier (lang:en) | dog breed (wd:Q39367) | England (wd:Q21) | 40.5 (xsd:decimal) | 15.4 (xsd:decimal) |
| Staffordshire Bull Terrier (lang:en) | dog breed (wd:Q39367) | England (wd:Q21) | 40.5 (xsd:decimal) | 17 (xsd:decimal)   |

[Assistant]
The query results confirm that the **Staffordshire Bull Terrier** is a dog breed originating from England. The height and mass have multiple values, which likely reflect variations in breed standards (e.g., males vs. females or different registries). The most commonly cited height is **35.5 cm to 40.5 cm**, and the mass ranges from **11 kg to 17 kg**.

Based on this information, I can now provide a clear and accurate answer to the question: "What are Staffordshire terriers?"

The term "Staffordshire terrier" commonly refers to the **Staffordshire Bull Terrier**, a breed of dog originating from England. It is a muscular, compact breed known for its loyalty and affectionate nature. It typically stands between 35.5 cm and 40.5 cm tall and weighs between 11 kg and 17 kg.

I will now finalize the SPARQL query and answer.

answer

SELECT ?label ?breed ?country ?height ?mass WHERE { wd:Q39285 rdfs:label ?label . FILTER(LANG(?label) = "en") . wd:Q39285 wdt:P31 ?breed . wd:Q39285 wdt:P495 ?country . wd:Q39285 wdt:P2048 ?height . wd:Q39285 wdt:P2067 ?mass . ?breed rdfs:label ?breedLabel . FILTER(LANG(?breedLabel) = "en") . ?country rdfs:label ?countryLabel . FILTER(LANG(?countryLabel) = "en") }

Answer: Staffordshire terriers commonly refer to the Staffordshire Bull Terrier, a breed of dog originating from England. It is a muscular, compact breed known for its loyalty and affectionate nature. It typically stands between 35.5 cm and 40.5 cm tall and weighs between 11 kg and 17 kg.