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 ?governmentType ?label WHERE {
  wd:Q155 wdt:P122 ?governmentType .
  ?governmentType rdfs:label ?label
  FILTER ( LANG( ?label ) = "en" )
}

Using entities:
- Brazil (wd:Q155), also known as br, Brasil, Federative Republic of Brazil: is instance of sovereign state / is instance of federal republic / is instance of Federal republic / is instance of country / is instance of rule of law / is instance of secular state / is instance of Secular state / country in South America / country in South America / country in South America / country in South America

Using properties:
- basic form of government (wd:P122 as wdt), also known as form of government, government, type of government, P122: subject's government / the subject's government / the subject's government

Got 3 rows and 2 columns:
| governmentType                        | label                              |
| ------------------------------------- | ---------------------------------- |
| representative democracy (wd:Q188759) | representative democracy (lang:en) |
| presidential system (wd:Q49892)       | presidential system (lang:en)      |
| federal republic (wd:Q512187)         | federal republic (lang:en)         |

Answer: Brazil's political system is a federal republic with a presidential system and representative democracy. The primary classification is a federal republic (wd:Q512187), which includes a presidential system (wd:Q49892) and representative democracy (wd:Q188759).

Brazil's political system is a federal republic with a presidential system and representative democracy. The primary classification is a federal republic (wd:Q512187), which includes a presidential system (wd:Q49892) and representative democracy (wd:Q188759).

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 ?governmentType ?label WHERE {
  wd:Q155 wdt:P122 ?governmentType .
  ?governmentType rdfs:label ?label
  FILTER ( LANG( ?label ) = "en" )
}

Using entities:
- Brazil (wd:Q155), also known as br, Brasil, Federative Republic of Brazil: is instance of sovereign state / is instance of federal republic / is instance of Federal republic / is instance of country / is instance of rule of law / is instance of secular state / is instance of Secular state / country in South America / country in South America / country in South America / country in South America

Using properties:
- basic form of government (wd:P122 as wdt), also known as form of government, government, type of government, P122: subject's government / the subject's government / the subject's government

Execution result:
Got 3 rows and 2 columns:
| governmentType                        | label                              |
| ------------------------------------- | ---------------------------------- |
| representative democracy (wd:Q188759) | representative democracy (lang:en) |
| presidential system (wd:Q49892)       | presidential system (lang:en)      |
| federal republic (wd:Q512187)         | federal republic (lang:en)         |

[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 type of political system is brazil?

[Assistant]
To determine the type of political system Brazil has, I need to find information about Brazil's government structure. This typically involves identifying the relevant property in Wikidata that describes the political system or government type of a country.

### Step 1: Search for the entity for Brazil
First, I will search for the Wikidata entity corresponding to Brazil.

Question: brazil

Top 10 entity alternatives:
1. Brazil (wd:Q155), also known as br, Brasil, Federative Republic of Brazil: is instance of Federal republic / is instance of federal republic / is instance of sovereign state / is instance of secular state / is instance of Secular state / is instance of rule of law / country in South America / country in South America / country in South America / country in South America / is instance of country
2. Brazil (wd:Q25057): 1985 dystopian film by Terry Gilliam / is instance of film
3. Brazil (wd:Q1998364), also known as Brazil, IN, Brazil, Indiana: city in Clay County, Indiana, United States / is instance of city in the United States / is instance of city of the United States
4. State of Brazil (wd:Q11876909, matched via Brazil), also known as Brazil, Colonial Brazil, Portuguese Brazil: is instance of historical country / state of the Portuguese Empire
5. Brazil (wd:Q4958616), also known as Stars and Guitars: 1944 film by Joseph Santley / is instance of film
6. Brazil (wd:Q17511873), also known as Brazil, IA: is instance of unincorporated community in the United States / human settlement in Appanoose County, Iowa, United States
7. Viceroyalty of Brazil (wd:Q2920081, matched via Brazil), also known as Brasil, Brazil: Portuguese viceroyalty in Brazil 1763-1815 / is instance of viceroyalty / is instance of Viceroyalty
8. Brazil (wd:Q13581616): is instance of musical work/composition / 1991 song by Bebi Dol
9. Brazil (wd:Q4095706): is instance of written work / 1994 novel by John Updike
10. Brésil (balloon) (wd:Q115682559, matched via Brazil), also known as Brazil: is instance of balloon / Spherical balloon

[Assistant]
The top result for Brazil is `wd:Q155`, which is described as the "Federative Republic of Brazil" and is an instance of a "Federal republic". This strongly suggests that Brazil's political system is a federal republic.

### Step 2: Confirm the political system property
To be thorough, I should confirm whether there is a specific property in Wikidata that represents the "political system" or "government type". I will search for properties related to "government" or "political system".

Question: political system

Top 10 property alternatives:
1. political ideology (wd:P1142 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn), also known as editorial viewpoint, has political ideology, ideology, official ideology, official political ideology, etc.: political ideology of an organization or person or of a work (such as a newspaper)
2. basic form of government (wd:P122 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn, matched via form of government), also known as form of government, government, type of government, P122: the subject's government / the subject's government / subject's government
3. member of political party (wd:P102 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn, matched via political party), also known as member of, member of party, party, party membership, political party, etc.: the political party of which a person is or has been a member or otherwise affiliated / the political party of which this politician is or has been a member / the political party of which this politician is or has been a member / is subproperty of member of
4. political alignment (wd:P1387 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn, matched via political position), also known as alignment, political position, P1387: political position within the left–right political spectrum
5. political coalition (wd:P5832 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn), also known as alliance, coalition, electoral alliance, electoral block, electoral list, etc.: agreement for cooperation between different political parties / is subproperty of member of
6. foundational text (wd:P457 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn, matched via constitution), also known as charter, constitution, constitutive text, created by, created in document, etc.: text through which an institution or object has been created or established / text through which an institution has been created
7. position held (wd:P39 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn, matched via political office held), also known as function, held position, holds position, job, office held, etc.: subject currently or formerly holds the object position or public office / subject currently or formerly holds the object position or public office / subject currently or formerly holds the object position or public office / subject currently or formerly holds the object position or public office
8. voting system (wd:P8196 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn, matched via electoral system), also known as electoral system, type of election, P8196: system used for this election or vote / system used for this election or vote
9. electoral symbol (wd:P12650 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn, matched via political symbol), also known as election symbol, political symbol, P12650: symbol allocated to a political party or candidate for use on ballots
10. diplomatic relation (wd:P530 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn, matched via political relation), also known as ambassadorial relation, ambassadorial relations, diplomatic relations, foreign relation, foreign relations, etc.: diplomatic relations of the country

[Assistant]
The property `wdt:P122` (basic form of government) is directly relevant to determining Brazil's political system. This property is described as "form of government" or "type of government", which is exactly what we need.

### Step 3: Query Brazil's form of government using wdt:P122
Now I will query Wikidata to retrieve Brazil's (wd:Q155) basic form of government using `wdt:P122`.

execute

SELECT ?governmentType WHERE { wd:Q155 wdt:P122 ?governmentType }

Got 3 rows and 1 column:
| governmentType                        |
| ------------------------------------- |
| representative democracy (wd:Q188759) |
| presidential system (wd:Q49892)       |
| federal republic (wd:Q512187)         |

[Assistant]
The query returns three values for Brazil's form of government:
1. **Representative democracy** (`wd:Q188759`)
2. **Presidential system** (`wd:Q49892`)
3. **Federal republic** (`wd:Q512187`)

These are not mutually exclusive — Brazil is a **federal republic** with a **presidential system** and operates as a **representative democracy**.

### Step 4: Retrieve human-readable labels for these government types
To provide a clear answer, I will fetch the English labels for these government types to confirm their meanings.

SELECT ?governmentType ?label WHERE { VALUES ?governmentType { wd:Q188759 wd:Q49892 wd:Q512187 } ?governmentType rdfs:label ?label FILTER(LANG(?label) = "en") }

Got 3 rows and 2 columns:
| governmentType                        | label                              |
| ------------------------------------- | ---------------------------------- |
| representative democracy (wd:Q188759) | representative democracy (lang:en) |
| presidential system (wd:Q49892)       | presidential system (lang:en)      |
| federal republic (wd:Q512187)         | federal republic (lang:en)         |

[Assistant]
The labels confirm the three aspects of Brazil's political system:

- **Federal republic**: Brazil is organized as a federation of states with a republican form of government (no monarchy).
- **Presidential system**: The president is both head of state and head of government, elected separately from the legislature.
- **Representative democracy**: Citizens elect representatives to make decisions on their behalf.

### Final Answer
Brazil's political system is a **federal republic** with a **presidential system** and operates as a **representative democracy**.

The most comprehensive single term describing Brazil’s system is **federal republic**, but it is accurate to describe it fully as a **federal presidential representative democratic republic**.

I will now provide the final SPARQL query and answer.

answer

SELECT ?governmentType ?label WHERE { wd:Q155 wdt:P122 ?governmentType . ?governmentType rdfs:label ?label FILTER(LANG(?label) = "en") }

Answer: Brazil's political system is a federal republic with a presidential system and representative democracy. The primary classification is a federal republic (wd:Q512187), which includes a presidential system (wd:Q49892) and representative democracy (wd:Q188759).


PREFIX p: <http://www.wikidata.org/prop/>
PREFIX ps: <http://www.wikidata.org/prop/statement/>
PREFIX wd: <http://www.wikidata.org/entity/>
SELECT ?date WHERE {
  wd:Q211386 p:P585 ?stmt .
  ?stmt ps:P585 ?date
}

Using entities:
- 1906 San Francisco earthquake (wd:Q211386), also known as 1906 San Francisco earthquake and fire, earthquake of 1906, Great 1906 San Francisco Earthquake, Great San Francisco Earthquake and Fire, San Francisco earthquake and fire, 1906, etc.: is instance of earthquake / is instance of Earthquake / major earthquake that struck San Francisco and the coast of Northern California

Using properties:
- point in time (wd:P585 as p/ps), 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

Answer: The big earthquake hit San Francisco on April 18, 1906.

The big earthquake hit San Francisco on April 18, 1906.

SPARQL query over wikidata:
PREFIX p: <http://www.wikidata.org/prop/>
PREFIX ps: <http://www.wikidata.org/prop/statement/>
PREFIX wd: <http://www.wikidata.org/entity/>
SELECT ?date WHERE {
  wd:Q211386 p:P585 ?stmt .
  ?stmt ps:P585 ?date
}

Using entities:
- 1906 San Francisco earthquake (wd:Q211386), also known as 1906 San Francisco earthquake and fire, earthquake of 1906, Great 1906 San Francisco Earthquake, Great San Francisco Earthquake and Fire, San Francisco earthquake and fire, 1906, etc.: is instance of earthquake / is instance of Earthquake / major earthquake that struck San Francisco and the coast of Northern California

Using properties:
- point in time (wd:P585 as p/ps), 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

Execution result:
Got 2 rows and 1 column:
| date                                |
| ----------------------------------- |
| 1906-04-18T00:00:00Z (xsd:dateTime) |
| 1906-04-18T00:00:00Z (xsd:dateTime) |

[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 did the big earthquake hit san francisco?

[Assistant]
To determine when the big earthquake hit San Francisco, I need to identify the specific earthquake event and its date. The most famous earthquake in San Francisco's history is the 1906 San Francisco earthquake. I will first search for information about this event in Wikidata.

Step 1: Search for the entity "1906 San Francisco earthquake" to find its Wikidata identifier.

Question: 1906 San Francisco earthquake

Top 10 entity alternatives:
1. 1906 San Francisco earthquake (wd:Q211386), also known as 1906 San Francisco earthquake and fire, earthquake of 1906, Great 1906 San Francisco Earthquake, Great San Francisco Earthquake and Fire, San Francisco earthquake and fire, 1906, etc.: major earthquake that struck San Francisco and the coast of Northern California / is instance of Earthquake / is instance of earthquake
2. The San Francisco earthquake of 1906 (wd:Q58176314): scholarly article by Dennis R. Dean published November 1993 in Annals of Science / is instance of scholarly article / is instance of academic article
3. The 1906 San Francisco Earthquake and Fire (wd:Q133012217): online exhibition from National Archives and Records Administration (United States) / is instance of online exhibition
4. Simulations of the 1906 San Francisco Earthquake (wd:Q57871965): scholarly article published 16 December 2005 / is instance of scholarly article / is instance of academic article
5. San Francisco Earthquake & Fire: April 18, 1906 (wd:Q19599178), also known as San Francisco Earthquake and Fire, April 18, 1906: is instance of short film / 1906 film
6. The 1906 San Francisco earthquake: a centennial contemplation. (wd:Q45948972): scientific article published in May 2006 / scientific article published in May 2006 / scientific article published in May 2006 / is instance of scholarly article / is instance of academic article
7. Postseismic deformation following the 1906 San Francisco earthquake (wd:Q97865309): scientific article published on 10 June 2000 / scientific article published on 10 June 2000 / scientific article published on 10 June 2000 / is instance of scholarly article / is instance of academic article
8. Source mechanism of the 1906 San Francisco earthquake (wd:Q98594973): scientific article published in September 1978 / scientific article published in September 1978 / scientific article published in September 1978 / is instance of scholarly article / is instance of academic article
9. Strain release mechanism of the 1906 san francisco earthquake (wd:Q57140054): is instance of scholarly article / is instance of academic article / scientific article
10. 1989 Loma Prieta earthquake (wd:Q1053476, matched via 1989 San Francisco earthquake), also known as 1989 San Francisco earthquake, Loma Prieta earthquake: major earthquake in northern California / major earthquake in northern California / is instance of natural disaster / is instance of Earthquake / is instance of earthquake / is instance of disaster

[Assistant]
The primary entity for the 1906 San Francisco earthquake is wd:Q211386. Now I will retrieve the date of this earthquake by checking its properties, particularly the start time (P580) or date (P585) if available.

Step 2: List the triples for the entity wd:Q211386 to find the date property.

list

wd:Q211386

Got 357 rows and 3 columns, showing the first 10 rows below:
| subject                                    | property                                                    | object                                                                              |
| ------------------------------------------ | ----------------------------------------------------------- | ----------------------------------------------------------------------------------- |
| 1906 San Francisco earthquake (wd:Q211386) | instance of (wdt:P31)                                       | earthquake (wd:Q7944)                                                               |
| 1906 San Francisco earthquake (wd:Q211386) | country (wdt:P17)                                           | United States (wd:Q30)                                                              |
| 1906 San Francisco earthquake (wd:Q211386) | located in the administrative territorial entity (wdt:P131) | California (wd:Q99)                                                                 |
| 1906 San Francisco earthquake (wd:Q211386) | coordinate location (wdt:P625)                              | POINT(-122.550000 37.750000) (geo:wktLiteral)                                       |
| 1906 San Francisco earthquake (wd:Q211386) | Commons category (wdt:P373)                                 | San Francisco earthquake of 1906                                                    |
| 1906 San Francisco earthquake (wd:Q211386) | image (wdt:P18)                                             | <http://commons.wikimedia.org/wiki/Special:FilePath/Post-and-Grant-Avenue-Look.jpg> |
| 1906 San Francisco earthquake (wd:Q211386) | Freebase ID (wdt:P646)                                      | /m/01f6rm                                                                           |
| 1906 San Francisco earthquake (wd:Q211386) | location (wdt:P276)                                         | San Francisco (wd:Q62)                                                              |
| 1906 San Francisco earthquake (wd:Q211386) | described by source (wdt:P1343)                             | San Francisco Earthquake & Fire: April 18, 1906 (wd:Q19599178)                      |
| 1906 San Francisco earthquake (wd:Q211386) | Library of Congress authority ID (wdtn:P244)                | <http://id.loc.gov/authorities/names/sh2003006458>                                  |
| ...                                        | ...                                                         | ...                                                                                |

[Assistant]
I see that the date of the earthquake is not directly listed in the triples. The property for the start time or date of the event is likely stored as a statement with qualifiers. I will search for properties related to the date or time of the earthquake.

Step 3: Search for properties related to the date or time of the earthquake for the entity wd:Q211386.

Question: date

Top 10 property alternatives:
1. point in time (wd:P585 as p/wdt, matched via date), 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
2. location (wd:P276 as p/wdt, matched via from), also known as based in, city, from, held by, in, etc.: location of the object, structure or event. In the case of an ... use P706. Use P7153 for locations associated with the object / location of the item, physical object or event is within. In ... use P131. In case of a distinct terrain feature use P706. / location of the item, physical object or event is within. In ... use P131. In case of a distinct terrain feature use P706.
3. coordinate location (wd:P625 as p/wdt, matched via position), also known as co-ordinate location, co-ordinates, coordinates, co-ords, coords, etc.: geocoordinates of the subject. For Earth, please note that only WGS84 coordinating system is supported at the moment / coordinates of the subject / coordinates of the subject
4. topic's main category (wd:P910 as p/wdt, matched via category), also known as article's main category, category, category for this topic, catmain, has category, etc.: main category of this topic / main Wikimedia category
5. instance of (wd:P31 as p/wdt, matched via type), 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. located in the administrative territorial entity (wd:P131 as p/wdt, matched via in), also known as administrative territorial entity, administrative territory, city, happens in, in, etc.: the item is located on the territory of the following ... the item falls only partially into the administrative entity. / the item is located on the territory of the following ... the item falls only partially into the administrative entity. / the item is located on the territory of the following administrative entity / the item is located on the territory of the following administrative entity / is subproperty of location / is subproperty of part of
7. described by source (wd:P1343 as p/wdt, matched via subject in), also known as defined in, described by biography, described by encyclopedia, described by obituary, described by reference work, etc.: dictionary, encyclopaedia, etc. where this item is described / work where this item is described / is subproperty of attested in
8. country (wd:P17 as p/wdt, matched via state), 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
9. has cause (wd:P828 as p/wdt, matched via cause), also known as because, cause, caused by, due to, effect of, etc.: underlying cause, entity that ultimately resulted in this effect / underlying cause, thing that ultimately resulted in this effect / is subproperty of follows
10. number of deaths (wd:P1120 as p/wdt, matched via death number), also known as dead, death count, death number, deaths, death toll, etc.: total (cumulative) number of people who died since start as a direct result of an event or cause / number of ALL people who died as a direct result of an event or cause / number of ALL people who died as a direct result of an event or cause

No other items found

[Assistant]
The property "point in time" (P585) is relevant for the date of the earthquake. I will now construct a SPARQL query to retrieve the date of the earthquake using the statement pattern with P585.

Step 4: Construct and execute a SPARQL query to get the date of the 1906 San Francisco earthquake using the P585 (point in time) property.

execute

SELECT ?date WHERE { wd:Q211386 p:P585 ?stmt . ?stmt ps:P585 ?date }

[Assistant]
The SPARQL query returned the date of the 1906 San Francisco earthquake as April 18, 1906 (1906-04-18T00:00:00Z). This matches the well-known historical event.

Now I will provide the final answer with the SPARQL query used.

answer

SELECT ?date WHERE { wd:Q211386 p:P585 ?stmt . ?stmt ps:P585 ?date }

Answer: The big earthquake hit San Francisco on April 18, 1906.


PREFIX wdt: <http://www.wikidata.org/prop/direct/>
PREFIX wd: <http://www.wikidata.org/entity/>
SELECT ?coordinates WHERE {
  wd:Q819 wdt:P625 ?coordinates
}

Using entities:
- Laos (wd:Q819), also known as la, LAO, Lao PDR, Lao People's Democratic Republic: is instance of landlocked country / is instance of sovereign state / is instance of people's republic / is instance of country / is instance of communist state / country in Southeast Asia / republic in Southeast Asia / republic in Southeast Asia

Using properties:
- coordinate location (wd:P625 as wdt), also known as co-ordinate location, co-ordinates, coordinates, co-ords, coords, etc.: coordinates of the subject / coordinates of the subject / geocoordinates of the subject. For Earth, please note that only WGS84 coordinating system is supported at the moment

Answer: Laos is located in Southeast Asia, centered at approximately 18.2° N latitude and 104.1° E longitude on the world map.

Laos is located in Southeast Asia, centered at approximately 18.2° N latitude and 104.1° E longitude on the world map.

SPARQL query over wikidata:
PREFIX wdt: <http://www.wikidata.org/prop/direct/>
PREFIX wd: <http://www.wikidata.org/entity/>
SELECT ?coordinates WHERE {
  wd:Q819 wdt:P625 ?coordinates
}

Using entities:
- Laos (wd:Q819), also known as la, LAO, Lao PDR, Lao People's Democratic Republic: is instance of landlocked country / is instance of sovereign state / is instance of people's republic / is instance of country / is instance of communist state / country in Southeast Asia / republic in Southeast Asia / republic in Southeast Asia

Using properties:
- coordinate location (wd:P625 as wdt), also known as co-ordinate location, co-ordinates, coordinates, co-ords, coords, etc.: coordinates of the subject / coordinates of the subject / geocoordinates of the subject. For Earth, please note that only WGS84 coordinating system is supported at the moment

Execution result:
Got 1 row and 1 column:
| coordinates                                  |
| -------------------------------------------- |
| POINT(104.100000 18.200000) (geo:wktLiteral) |

[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] where is laos in world map?

[Assistant]
To determine where Laos is on the world map, I need to find the geographic location of Laos, which is typically represented by its coordinates (latitude and longitude) or its position relative to other countries.

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

Question: laos

Top 10 entity alternatives:
1. Laos (wd:Q819), also known as la, LAO, Lao PDR, Lao People's Democratic Republic: is instance of landlocked country / is instance of people's republic / is instance of sovereign state / is instance of communist state / republic in Southeast Asia / republic in Southeast Asia / country in Southeast Asia / is instance of country
2. Tai peoples (wd:Q703353, matched via Laos), also known as Laos, Shans: is subclass of group of humans / is instance of panethnicity / Wikimedia category / Wikimedia category / ethnic group
3. Laotians (wd:Q11346642, matched via Laos), also known as Lao, Laos: is subclass of South-East Asians / is instance of human population / is subclass of Southeast Asians / citizens or residents of Laos / is subclass of Asian people / is subclass of Francophone / is instance of Population / is instance of population / is subclass of inhabitant
4. Laos (wd:Q28322504): is instance of family name / is instance of surname / family name / family name / surname
5. Laos (wd:Q3217694): is instance of musical group / German hard rock band
6. Laos (wd:Q130900075): scientific article published in January 2003 / is instance of scholarly article / is instance of academic article
7. Laos (wd:Q130740644): scientific article published in January 2001 / is instance of scholarly article / is instance of academic article
8. Laos (wd:Q123985601): is instance of male given name / male given name
9. Laos (wd:Q130639957): scientific article published in January 1999 / is instance of scholarly article / is instance of academic article
10. Laos (wd:Q103947900): is instance of encyclopaedic article / is instance of encyclopedia article / encyclopedia article

[Assistant]
The correct entity for the country Laos is `wd:Q819`, which is described as a landlocked country, a sovereign state, and a republic in Southeast Asia. This is the most relevant entity for our purpose.

### Step 2: Find the geographic coordinates of Laos
Now, I will check the properties of Laos (`wd:Q819`) to find its geographic coordinates. The property for coordinates in Wikidata is `wdt:P625`.

I will execute a query to retrieve the coordinates of Laos.

execute

SELECT ?coordinates WHERE { wd:Q819 wdt:P625 ?coordinates }

[Assistant]
The geographic coordinates of Laos are approximately **18.2° N (latitude)** and **104.1° E (longitude)**. These coordinates place Laos in **Southeast Asia**, bordered by China to the north, Vietnam to the east, Cambodia to the south, Thailand to the west, and Myanmar to the northwest.

### Final Answer:
Laos is located in Southeast Asia, centered at approximately **18.2° N latitude** and **104.1° E longitude** on the world map.

I will now provide the final SPARQL query and answer.

answer

SELECT ?coordinates WHERE { wd:Q819 wdt:P625 ?coordinates }

Answer: Laos is located in Southeast Asia, centered at approximately 18.2° N latitude and 104.1° E longitude on the world map.


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 ?place ?placeLabel WHERE {
  wd:Q1035 wdt:P20 ?place .
  ?place rdfs:label ?placeLabel .
  FILTER ( LANG( ?placeLabel ) = "en" )
}

Using entities:
- Charles Darwin (wd:Q1035): has occupation writer / has occupation geologist / has occupation Philosopher / has occupation philosopher / has occupation explorer / has occupation travel writer / has occupation botanist / has occupation naturalist / has occupation ethologist / is instance of human / English naturalist and biologist (1809–1882) / English naturalist and biologist (1809–1882)

Using properties:
- place of death (wd:P20 as wdt), also known as death location, death place, deathplace, died, died in, etc.: is subproperty of location / most specific known (e.g. city instead of country, or ... death location of a person, animal or fictional character / most specific known (e.g. city instead of country, or ... death location of a person, animal or fictional character / most specific known (e.g. city instead of country, or ... death location of a person, animal or fictional character

Answer: Charles Darwin died at Down House.

Charles Darwin died at Down House.

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 ?place ?placeLabel WHERE {
  wd:Q1035 wdt:P20 ?place .
  ?place rdfs:label ?placeLabel .
  FILTER ( LANG( ?placeLabel ) = "en" )
}

Using entities:
- Charles Darwin (wd:Q1035): has occupation writer / has occupation geologist / has occupation Philosopher / has occupation philosopher / has occupation explorer / has occupation travel writer / has occupation botanist / has occupation naturalist / has occupation ethologist / is instance of human / English naturalist and biologist (1809–1882) / English naturalist and biologist (1809–1882)

Using properties:
- place of death (wd:P20 as wdt), also known as death location, death place, deathplace, died, died in, etc.: is subproperty of location / most specific known (e.g. city instead of country, or ... death location of a person, animal or fictional character / most specific known (e.g. city instead of country, or ... death location of a person, animal or fictional character / most specific known (e.g. city instead of country, or ... death location of a person, animal or fictional character

Execution result:
Got 1 row and 2 columns:
| place                    | placeLabel           |
| ------------------------ | -------------------- |
| Down House (wd:Q3038318) | Down House (lang:en) |

[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] where did charles darwin die?

[Assistant]
To determine where Charles Darwin died, I need to find the place of death for Charles Darwin. Let's follow the steps:

1. First, I'll search for the entity "Charles Darwin" in Wikidata to get its identifier.
2. Then, I'll look for the property related to "place of death" for this entity.
3. Finally, I'll construct a SPARQL query to retrieve the place of death.

Let me start by searching for Charles Darwin:

Question: charles darwin

Top 10 entity alternatives:
1. Charles Darwin (wd:Q1035): English naturalist and biologist (1809–1882) / English naturalist and biologist (1809–1882) / has occupation travel writer / has occupation Philosopher / has occupation philosopher / has occupation ethologist / has occupation naturalist / has occupation geologist / has occupation explorer / has occupation botanist / has occupation writer / is instance of human
2. Charles Galton Darwin (wd:Q1064506, matched via Charles Darwin), also known as Charles Darwin, Sir Charles Galton Darwin: has occupation university teacher / British physicist (1887–1962) / has occupation physicist / is instance of human / British physicist / British physicist
3. Charles Darwin (wd:Q5076724): oldest son of Erasmus Darwin and uncle of the naturalist Charles Darwin / has occupation physician / has occupation writer / is instance of human
4. Darwin, Charles (wd:Q107131027): entry in Alumni Oxonienses: the Members of the University of Oxford, 1715-1886 / is instance of biographical article
5. Charles Darwin (wd:Q19153034): German article in Die Gartenlaube, 1882, no. 19 / is instance of article
6. Charles Darwin (wd:Q15873833): is instance of album / album by XII Alfonso
7. Charles Darwin (wd:Q5076727), also known as Charles Darwin, Northern Territory, Charles Darwin, Northern Territory, Australia: location in Northern Territory, Australia / is instance of locality
8. Charles Darwin (wd:Q5076728): has occupation military personnel / has occupation Military personnel / is instance of human / British flying ace / British flying ace / British flying ace
9. Charles Darwin (wd:Q123948989): street in Sofia, Bulgaria / is instance of street
10. Charles Darwin (wd:Q108628723): statue in Shrewsbury, Great Britain - Jemma Pearson - 2000 / is instance of sculpture

[Assistant]
I see that the first result (wd:Q1035) is the correct Charles Darwin - the English naturalist and biologist (1809–1882). Let me verify this is the right entity by checking some of its properties, particularly to confirm it's a human and to look for the place of death property.

Let me list some properties of this entity:

list

wd:Q1035

[Assistant]
Good, this confirms that wd:Q1035 is indeed a human (wd:Q5), which is the correct Charles Darwin we're looking for.

Now, let me search for the property related to "place of death" to find the correct property identifier:

Question: place of death

Top 10 property alternatives:
1. place of death (wd:P20 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn), also known as death location, death place, deathplace, died, died in, etc.: most specific known (e.g. city instead of country, or ... death location of a person, animal or fictional character / most specific known (e.g. city instead of country, or ... death location of a person, animal or fictional character / most specific known (e.g. city instead of country, or ... death location of a person, animal or fictional character / is subproperty of location
2. place of burial (wd:P119 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn), also known as ashes scattered at, burial location, burial place, buried at, buried in, etc.: location of grave, resting place, place of ash-scattering, ... places: e.g., re-burials, parts of body buried separately. / location of grave, resting place, place of ash-scattering, ... places: e.g., re-burials, parts of body buried separately. / location of grave, resting place, place of ash-scattering, ... e.g. re-burials, cenotaphs, parts of body buried separately / location of grave, resting place, place of ash-scattering, etc, (e.g. city or cemetery) for a person / is subproperty of location
3. category for people who died here (wd:P1465 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn, matched via category for place of death), also known as category for place of death, category of people who died here, P1465: category item for people who died in this location / is subproperty of related category
4. place of disappearance (wd:P10642 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn), also known as P10642: place where people or things have disappeared; link with P746 (date of disappearance)
5. date of death (wd:P570 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn), also known as date of the end, dead, death, death date, deathdate, etc.: is subproperty of dissolved, abolished or demolished date / is subproperty of dissolved, abolished or demolished / date on which the subject died / date on which the subject died / date on which the subject died / is subproperty of end time
6. number of deaths (wd:P1120 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn, matched via deaths), also known as dead, death count, death number, deaths, death toll, etc.: total (cumulative) number of people who died since start as a direct result of an event or cause / number of ALL people who died as a direct result of an event or cause / number of ALL people who died as a direct result of an event or cause
7. manner of death (wd:P1196 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn, matched via type of death), also known as circumstance of death, death manner, death type, nature of death, type of death, etc.: general circumstances of a person's death; e.g. natural ... mechanism, e.g. heart attack, trauma, pneumonia etc. / general circumstances of a person's death; e.g. natural ... mechanism, e.g. heart attack, trauma, pneumonia etc. / general circumstances of a person's death; e.g. natural ... mechanism, e.g. heart attack, trauma, pneumonia...
8. place of birth (wd:P19 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn), also known as birth city, birth location, birth place, birthplace, born, etc.: most specific known (e.g. city instead of country, or ... birth location of a person, animal or fictional character / most specific known (e.g. city instead of country, or ... birth location of a person, animal or fictional character / most specific known birth location of a person, animal or fictional character / is subproperty of location
9. date of burial or cremation (wd:P4602 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn), also known as burial date, cremation date, date of cremation, funeral date, P4602: date on which the person was buried or cremated soon after death / is subproperty of point in time
10. applies to jurisdiction (wd:P1001 as ps/psv/p/pqv/pqn/psn/pq/wdt/pr/prn/prv/wdtn, matched via of place), also known as applicable area, applicable country, applicable geographic place, applicable jurisdiction, applicable location, etc.: the item (institution, law, public office, public ... jurisdiction: a country, state, municipality, ...) / the item (an institution, law, public office ...) or ... jurisdiction: a country, state, municipality, ...) / is subproperty of significant place / is subproperty of characteristic of / is subproperty of operating area

[Assistant]
I see that the property "place of death" is P20 (wd:P20). Now I can construct a SPARQL query to find where Charles Darwin died.

The query will:
1. Use wd:Q1035 as the subject (Charles Darwin)
2. Use wdt:P20 to get the place of death
3. Retrieve the label of the place in English for better readability

Let me execute this query:

execute

SELECT ?place ?placeLabel WHERE { wd:Q1035 wdt:P20 ?place . SERVICE wikibase:label { bd:serviceParam wikibase:language "en". } }

SPARQL execution failed:
Error while executing a SERVICE request to <http://wikiba.se:80/ontology#label>: SERVICE responded with HTTP status code: 301, Moved Permanently. First 100 bytes of the response: '
<title>301 Moved Permanently</title>

301 Moved Permanently'

[Assistant]
I see that the SERVICE wikibase:label syntax is not supported in this environment. I need to use rdfs:label instead with a language filter.

Let me modify the query to use rdfs:label with a language filter for English:

SELECT ?place ?placeLabel WHERE { wd:Q1035 wdt:P20 ?place . ?place rdfs:label ?placeLabel . FILTER(LANG(?placeLabel) = "en") }

[Assistant]
I now have the answer. Charles Darwin died at Down House.

Let me verify this is correct by checking what Down House is:

list

wd:Q3038318

Got 186 rows and 3 columns, showing the first 10 rows below:
| subject                  | property                                                    | object                                                                |
| ------------------------ | ----------------------------------------------------------- | --------------------------------------------------------------------- |
| Down House (wd:Q3038318) | instance of (wdt:P31)                                       | historic house museum (wd:Q2087181)                                   |
| Down House (wd:Q3038318) | country (wdt:P17)                                           | United Kingdom (wd:Q145)                                              |
| Down House (wd:Q3038318) | located in the administrative territorial entity (wdt:P131) | London Borough of Bromley (wd:Q208201)                                |
| Down House (wd:Q3038318) | coordinate location (wdt:P625)                              | POINT(0.053333 51.331389) (geo:wktLiteral)                            |
| Down House (wd:Q3038318) | Commons category (wdt:P373)                                 | Down House                                                            |
| Down House (wd:Q3038318) | image (wdt:P18)                                             | <http://commons.wikimedia.org/wiki/Special:FilePath/Down%20House.jpg> |
| Down House (wd:Q3038318) | Freebase ID (wdt:P646)                                      | /m/02_675                                                             |
| Down House (wd:Q3038318) | location (wdt:P276)                                         | Downe (wd:Q125344)                                                    |
| Down House (wd:Q3038318) | VIAF cluster ID (wdtn:P214)                                 | <http://viaf.org/viaf/241907195>                                      |
| Down House (wd:Q3038318) | heritage designation (wdt:P1435)                            | Tentative World Heritage Site (wd:Q1459900)                           |
| ...                      | ...                                                         | ...                                                                   |

[Assistant]
I can see that Down House (wd:Q3038318) is a historic house museum located in the London Borough of Bromley, United Kingdom. This confirms that Charles Darwin died at Down House, which was his home.

Now I'll provide the final answer with the SPARQL query:

answer

SELECT ?place ?placeLabel WHERE { wd:Q1035 wdt:P20 ?place . ?place rdfs:label ?placeLabel . FILTER(LANG(?placeLabel) = "en") }

Answer: Charles Darwin died at Down House.