PREFIX wdt: <http://www.wikidata.org/prop/direct/>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
SELECT ?item ?cleanLabel WHERE {
  ?item rdfs:label ?label .
  FILTER ( LANG( ?label ) = "en" ) .
  FILTER ( STRSTARTS( ?label , "Erratum: " ) ) . MINUS {
    ?otherItem wdt:P2507 ?item
  }
  .
  BIND( REPLACE( ?label , "Erratum: " , "" ) AS ?cleanLabel ) .
  FILTER ( STRLEN( ?cleanLabel ) > 20 )
}

Using properties:
- corrigendum / erratum (wd:P2507 as wdt), also known as corrected by, corrigenda, corrigendum, errata, erratum, etc.: a published correction to a previous publication / published notice that corrects or amends a previous publication

Got 5,640 rows and 2 columns, showing the first 5 and last 5 rows below:
| item                                                                                | cleanLabel                                                                                |
| ------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------- |
| Erratum: Novel Aptamer-Functionalized Nanoparticles Enhances Bone Defect Repair by Improving Stem Cell Recruitment [Corrigendum] (wd:Q100298620) | Novel Aptamer-Functionalized Nanoparticles Enhances Bone Defect Repair by Improving Stem Cell Recruitment [Corrigendum] (lang:en) |
| Erratum: Iron Oxide Nanoparticles Promote the Migration of Mesenchymal Stem Cells to Injury Sites [Corrigendum] (wd:Q100298621)                  | Iron Oxide Nanoparticles Promote the Migration of Mesenchymal Stem Cells to Injury Sites [Corrigendum] (lang:en)                  |
| Erratum: Fabrication and Characterization of Glimepiride ... and in vitro α-Glucosidase Inhibition [Corrigendum] (wd:Q100298624)                 | Fabrication and Characterization of Glimepiride ... and in vitro α-Glucosidase Inhibition [Corrigendum] (lang:en)                 |
| Erratum: Oral Administration of Encapsulated Bovine ... Intracellular Parasite Toxoplasma gondii [Corrigendum] (wd:Q100298692)                   | Oral Administration of Encapsulated Bovine Lactoferrin ... Intracellular Parasite Toxoplasma gondii [Corrigendum] (lang:en)       |
| Erratum: A Predictive Model Offor Attention Deficit Hyperactivity Disorder Based on Clinical Assessment Tools [Corrigendum] (wd:Q100298712)      | A Predictive Model Offor Attention Deficit Hyperactivity Disorder Based on Clinical Assessment Tools [Corrigendum] (lang:en)      |
| ...                                                                                | ...                                                                                |
| Erratum: Meyer, J., et al. Changes in Physical Activity and ... Int. J. Environ. Res. Public Health 2020, 17(18), 6469 (wd:Q99725289)            | Meyer, J., et al. Changes in Physical Activity and Sedentary ... Int. J. Environ. Res. Public Health 2020, 17(18), 6469 (lang:en) |
| Erratum: Witschen, P.M., et al. Tumor Cell Associated ... Inflammation in Breast Cancer. Cancers 2020, 12, 1325 (wd:Q99726039)                   | Witschen, P.M., et al. Tumor Cell Associated Hyaluronan-CD44 ... Inflammation in Breast Cancer. Cancers 2020, 12, 1325 (lang:en)  |
| Erratum: Comparative ecology of Quebec boreal forests: a numerical approach to modelling (wd:Q99868507)                                          | Comparative ecology of Quebec boreal forests: a numerical approach to modelling (lang:en)                                         |
| Erratum: A method for the extraction of chlorophyll from leaf tissue without maceration (wd:Q99868747)                                           | A method for the extraction of chlorophyll from leaf tissue without maceration (lang:en)                                          |
| Erratum: Validation of Pythium delawarii as Pythium delawarense sp. nov. (wd:Q99887878)                                                          | Validation of Pythium delawarii as Pythium delawarense sp. nov. (lang:en)                                                         |

Answer:
There are 5,640 errata (published corrections) with English labels starting with "Erratum: " that are not referenced by any other item using the "corrigendum / erratum" property (wdt:P2507). Each has a cleaned label (after removing "Erratum: ") longer than 20 characters. Examples include:

- Item: wd:Q100298620, Label: "Novel Aptamer-Functionalized Nanoparticles Enhances Bone Defect Repair by Improving Stem Cell Recruitment [Corrigendum]"
- Item: wd:Q99868747, Label: "A method for the extraction of chlorophyll from leaf tissue without maceration"

The full list can be retrieved by executing the provided SPARQL query.

There are 5,640 errata (published corrections) with English labels starting with "Erratum: " that are not referenced by any other item using the "corrigendum / erratum" property (wdt:P2507). Each has a cleaned label (after removing "Erratum: ") longer than 20 characters. Examples include:

- Item: wd:Q100298620, Label: "Novel Aptamer-Functionalized Nanoparticles Enhances Bone Defect Repair by Improving Stem Cell Recruitment [Corrigendum]"
- Item: wd:Q99868747, Label: "A method for the extraction of chlorophyll from leaf tissue without maceration"

The full list can be retrieved by executing the provided SPARQL query.

SPARQL query over wikidata:
PREFIX wdt: <http://www.wikidata.org/prop/direct/>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
SELECT ?item ?cleanLabel WHERE {
  ?item rdfs:label ?label .
  FILTER ( LANG( ?label ) = "en" ) .
  FILTER ( STRSTARTS( ?label , "Erratum: " ) ) . MINUS {
    ?otherItem wdt:P2507 ?item
  }
  .
  BIND( REPLACE( ?label , "Erratum: " , "" ) AS ?cleanLabel ) .
  FILTER ( STRLEN( ?cleanLabel ) > 20 )
}

Using properties:
- corrigendum / erratum (wd:P2507 as wdt), also known as corrected by, corrigenda, corrigendum, errata, erratum, etc.: a published correction to a previous publication / published notice that corrects or amends a previous publication

Execution result:
Got 5,640 rows and 2 columns, showing the first 5 and last 5 rows below:
| item                                                                                | cleanLabel                                                                                |
| ------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------- |
| Erratum: Novel Aptamer-Functionalized Nanoparticles Enhances Bone Defect Repair by Improving Stem Cell Recruitment [Corrigendum] (wd:Q100298620) | Novel Aptamer-Functionalized Nanoparticles Enhances Bone Defect Repair by Improving Stem Cell Recruitment [Corrigendum] (lang:en) |
| Erratum: Iron Oxide Nanoparticles Promote the Migration of Mesenchymal Stem Cells to Injury Sites [Corrigendum] (wd:Q100298621)                  | Iron Oxide Nanoparticles Promote the Migration of Mesenchymal Stem Cells to Injury Sites [Corrigendum] (lang:en)                  |
| Erratum: Fabrication and Characterization of Glimepiride ... and in vitro α-Glucosidase Inhibition [Corrigendum] (wd:Q100298624)                 | Fabrication and Characterization of Glimepiride ... and in vitro α-Glucosidase Inhibition [Corrigendum] (lang:en)                 |
| Erratum: Oral Administration of Encapsulated Bovine ... Intracellular Parasite Toxoplasma gondii [Corrigendum] (wd:Q100298692)                   | Oral Administration of Encapsulated Bovine Lactoferrin ... Intracellular Parasite Toxoplasma gondii [Corrigendum] (lang:en)       |
| Erratum: A Predictive Model Offor Attention Deficit Hyperactivity Disorder Based on Clinical Assessment Tools [Corrigendum] (wd:Q100298712)      | A Predictive Model Offor Attention Deficit Hyperactivity Disorder Based on Clinical Assessment Tools [Corrigendum] (lang:en)      |
| ...                                                                                | ...                                                                                |
| Erratum: Meyer, J., et al. Changes in Physical Activity and ... Int. J. Environ. Res. Public Health 2020, 17(18), 6469 (wd:Q99725289)            | Meyer, J., et al. Changes in Physical Activity and Sedentary ... Int. J. Environ. Res. Public Health 2020, 17(18), 6469 (lang:en) |
| Erratum: Witschen, P.M., et al. Tumor Cell Associated ... Inflammation in Breast Cancer. Cancers 2020, 12, 1325 (wd:Q99726039)                   | Witschen, P.M., et al. Tumor Cell Associated Hyaluronan-CD44 ... Inflammation in Breast Cancer. Cancers 2020, 12, 1325 (lang:en)  |
| Erratum: Comparative ecology of Quebec boreal forests: a numerical approach to modelling (wd:Q99868507)                                          | Comparative ecology of Quebec boreal forests: a numerical approach to modelling (lang:en)                                         |
| Erratum: A method for the extraction of chlorophyll from leaf tissue without maceration (wd:Q99868747)                                           | A method for the extraction of chlorophyll from leaf tissue without maceration (lang:en)                                          |
| Erratum: Validation of Pythium delawarii as Pythium delawarense sp. nov. (wd:Q99887878)                                                          | Validation of Pythium delawarii as Pythium delawarense sp. nov. (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 are the errata (published corrections to previous publications) with English labels starting with "Erratum:" that are not referenced by any item using the "corrigendum / erratum" property? Also, provide their corresponding item labels (after removing the "Erratum: " prefix) and items, where the item labels are longer than 20 characters.

[Assistant]
To answer this question, I need to find errata (published corrections to previous publications) in Wikidata that meet the following criteria:

1. They have English labels starting with "Erratum: ".
2. They are **not referenced by any item** using the "corrigendum / erratum" property (i.e., no other item uses the property `wdt:P732` to point to them).
3. Their labels, after removing the "Erratum: " prefix, are longer than 20 characters.
4. Return the corrected label (without "Erratum: ") and the item IRI.

### Step 1: Understand the "corrigendum / erratum" property
I need to confirm the property for "corrigendum / erratum". Let me search for it.

Question: corrigendum erratum

Top 10 property alternatives:
1. corrigendum / erratum (wd:P2507 as psn/wdtn/p/prv/prn/pq/ps/psv/pr/wdt/pqn/pqv), also known as corrected by, corrigenda, corrigendum, errata, erratum, etc.: published notice that corrects or amends a previous publication / a published correction to a previous publication
2. amended by (wd:P2567 as psn/wdtn/p/prv/prn/pq/ps/psv/pr/wdt/pqn/pqv, matched via corrected by), also known as altered by, changed by, corrected by, has addendum, modified by, etc.: document is amended by specified other document
3. front and back matter (wd:P8570 as psn/wdtn/p/prv/prn/pq/ps/psv/pr/wdt/pqn/pqv, matched via addendum), also known as abbreviations table, acknowledgment, addendum, afterword, appendix, etc.: is subproperty of has part(s) of the class / is subproperty of has parts of the class / front and back matter of a book
4. last update (wd:P5017 as psn/wdtn/p/prv/prn/pq/ps/psv/pr/wdt/pqn/pqv, matched via revised), also known as altered, altered last, changed, changed last, last changed, etc.: date a reference was modified, revised, or updated
5. modified version of (wd:P5059 as psn/wdtn/p/prv/prn/pq/ps/psv/pr/wdt/pqn/pqv, matched via modification of), also known as adaptation of, arrangement of, fork of, modification of, revised version of, etc.: indicates the work or one of its versions which served as a ... or arrangement resulting in the given version of the work / is subproperty of based on
6. reference URL (wd:P854 as psn/wdtn/p/prv/prn/pq/ps/psv/pr/wdt/pqn/pqv, matched via ref), also known as ref, site, URL, URL fonte, URL ref, etc.: should be used for Internet URLs as references. Use "Wikimedia import URL" (P4656) for imports from WMF sites / should be used for Internet URLs as references. Use "Wikimedia import URL" (P4656) for interwiki links / should be used for Internet URLs as references. Use P4656 for interwiki links / is subproperty of URL
7. has edition or translation (wd:P747 as psn/wdtn/p/prv/prn/pq/ps/psv/pr/wdt/pqn/pqv, matched via modified as), also known as arranged as, arrangement, edition, edition or translation, editions, etc.: item that is an edition or translation of this item
8. reissue of (wd:P9237 as psn/wdtn/p/prv/prn/pq/ps/psv/pr/wdt/pqn/pqv, matched via re-edition), also known as re-edition, repackage, re-release, P9237: reissue of musical work, release
9. retracted by (wd:P5824 as psn/wdtn/p/prv/prn/pq/ps/psv/pr/wdt/pqn/pqv), also known as P5824: (article) is retracted by (retraction notice)
10. inventory number (wd:P217 as psn/wdtn/p/prv/prn/pq/ps/psv/pr/wdt/pqn/pqv, matched via reference), also known as accession number, call number, catalog number, catalogue number, collection number, etc.: identifier for a physical object or a set of physical objects in a collection / identifier for a physical object or a set of physical objects in a collection

[Assistant]
The property for "corrigendum / erratum" is `wdt:P2507` (also known as "corrected by"). This property links a corrected publication to the erratum/corrigendum that fixes it.

So, if an item `X` is an erratum, then other items (the corrected publications) will have `wdt:P2507` pointing to `X`.

We want errata items that are **not referenced** by any other item via `wdt:P2507`.

### Step 2: Find items with English labels starting with "Erratum: "

I will construct a SPARQL query to:
- Select items with English labels starting with "Erratum: "
- Filter out those that are referenced by any item via `wdt:P2507`
- Remove the "Erratum: " prefix from the label
- Ensure the resulting label is longer than 20 characters
- Return the cleaned label and the item IRI

### Step 3: Build the SPARQL query

I'll use:
- `rdfs:label` with `FILTER(LANG(?label) = "en")` to get English labels
- `FILTER(STRSTARTS(?label, "Erratum: "))` to match the prefix
- Use `MINUS` to exclude items that are the object of `wdt:P2507` (i.e., not referenced by any item)
- Use `REPLACE(?label, "Erratum: ", "")` to remove the prefix
- Use `strlen()` to filter labels longer than 20 characters

Let me write and test the query.

execute

SELECT ?item ?cleanLabel WHERE { ?item rdfs:label ?label . FILTER(LANG(?label) = "en") . FILTER(STRSTARTS(?label, "Erratum: ")) . MINUS { ?otherItem wdt:P2507 ?item } . BIND(REPLACE(?label, "Erratum: ", "") AS ?cleanLabel) . FILTER(STRLEN(?cleanLabel) > 20) }

Got 5,640 rows and 2 columns, showing the first 5 and last 5 rows below:
| item                                                                                | cleanLabel                                                                                |
| ------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------- |
| Erratum: Novel Aptamer-Functionalized Nanoparticles Enhances Bone Defect Repair by Improving Stem Cell Recruitment [Corrigendum] (wd:Q100298620) | Novel Aptamer-Functionalized Nanoparticles Enhances Bone Defect Repair by Improving Stem Cell Recruitment [Corrigendum] (lang:en) |
| Erratum: Iron Oxide Nanoparticles Promote the Migration of Mesenchymal Stem Cells to Injury Sites [Corrigendum] (wd:Q100298621)                  | Iron Oxide Nanoparticles Promote the Migration of Mesenchymal Stem Cells to Injury Sites [Corrigendum] (lang:en)                  |
| Erratum: Fabrication and Characterization of Glimepiride ... and in vitro α-Glucosidase Inhibition [Corrigendum] (wd:Q100298624)                 | Fabrication and Characterization of Glimepiride ... and in vitro α-Glucosidase Inhibition [Corrigendum] (lang:en)                 |
| Erratum: Oral Administration of Encapsulated Bovine ... Intracellular Parasite Toxoplasma gondii [Corrigendum] (wd:Q100298692)                   | Oral Administration of Encapsulated Bovine Lactoferrin ... Intracellular Parasite Toxoplasma gondii [Corrigendum] (lang:en)       |
| Erratum: A Predictive Model Offor Attention Deficit Hyperactivity Disorder Based on Clinical Assessment Tools [Corrigendum] (wd:Q100298712)      | A Predictive Model Offor Attention Deficit Hyperactivity Disorder Based on Clinical Assessment Tools [Corrigendum] (lang:en)      |
| ...                                                                                | ...                                                                                |
| Erratum: Meyer, J., et al. Changes in Physical Activity and ... Int. J. Environ. Res. Public Health 2020, 17(18), 6469 (wd:Q99725289)            | Meyer, J., et al. Changes in Physical Activity and Sedentary ... Int. J. Environ. Res. Public Health 2020, 17(18), 6469 (lang:en) |
| Erratum: Witschen, P.M., et al. Tumor Cell Associated ... Inflammation in Breast Cancer. Cancers 2020, 12, 1325 (wd:Q99726039)                   | Witschen, P.M., et al. Tumor Cell Associated Hyaluronan-CD44 ... Inflammation in Breast Cancer. Cancers 2020, 12, 1325 (lang:en)  |
| Erratum: Comparative ecology of Quebec boreal forests: a numerical approach to modelling (wd:Q99868507)                                          | Comparative ecology of Quebec boreal forests: a numerical approach to modelling (lang:en)                                         |
| Erratum: A method for the extraction of chlorophyll from leaf tissue without maceration (wd:Q99868747)                                           | A method for the extraction of chlorophyll from leaf tissue without maceration (lang:en)                                          |
| Erratum: Validation of Pythium delawarii as Pythium delawarense sp. nov. (wd:Q99887878)                                                          | Validation of Pythium delawarii as Pythium delawarense sp. nov. (lang:en)                                                         |

[Assistant]
The query executed successfully and returned 5,640 results. All results meet the criteria:

- They are items with English labels starting with "Erratum: "
- They are **not referenced** by any other item via `wdt:P2507` (i.e., no other item uses them as a corrigendum/erratum)
- The cleaned label (after removing "Erratum: ") is longer than 20 characters (as confirmed by the sample results)

The results include academic paper corrigenda with titles like:
- "Novel Aptamer-Functionalized Nanoparticles Enhances Bone Defect Repair by Improving Stem Cell Recruitment [Corrigendum]"
- "A method for the extraction of chlorophyll from leaf tissue without maceration"

These are all valid errata that are not being used as references by other items — meaning they are "orphaned" errata in the knowledge graph.

### Final Answer

The SPARQL query correctly identifies all such errata. The results include the item IRI and the cleaned label (without "Erratum: "), and all cleaned labels are longer than 20 characters.

I will now provide the final answer.

answer

SELECT ?item ?cleanLabel WHERE { ?item rdfs:label ?label . FILTER(LANG(?label) = "en") . FILTER(STRSTARTS(?label, "Erratum: ")) . MINUS { ?otherItem wdt:P2507 ?item } . BIND(REPLACE(?label, "Erratum: ", "") AS ?cleanLabel) . FILTER(STRLEN(?cleanLabel) > 20) }

Answer:
There are 5,640 errata (published corrections) with English labels starting with "Erratum: " that are not referenced by any other item using the "corrigendum / erratum" property (wdt:P2507). Each has a cleaned label (after removing "Erratum: ") longer than 20 characters. Examples include:

- Item: wd:Q100298620, Label: "Novel Aptamer-Functionalized Nanoparticles Enhances Bone Defect Repair by Improving Stem Cell Recruitment [Corrigendum]"
- Item: wd:Q99868747, Label: "A method for the extraction of chlorophyll from leaf tissue without maceration"

The full list can be retrieved by executing the provided SPARQL query.


PREFIX wdt: <http://www.wikidata.org/prop/direct/>
PREFIX geof: <http://www.opengis.net/def/function/geosparql/>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX wd: <http://www.wikidata.org/entity/>
SELECT ?commune ?communeLabel ?lat ?lon WHERE {
  ?commune wdt:P31 wd:Q15284 ; wdt:P17 wd:Q38 ; wdt:P625 ?coord .
  BIND( geof:latitude ( ?coord ) AS ?lat ) BIND( geof:longitude ( ?coord ) AS ?lon ) ?commune rdfs:label ?communeLabel .
  FILTER ( LANG( ?communeLabel ) = "en" ) FILTER ( ?lat > 45.650278 )
}
ORDER BY DESC ( ?lat )

Using entities:
- municipality (wd:Q15284), also known as municipalities: is instance of administrative territorial entity type / is subclass of political territorial entity / is subclass of government organisation / is subclass of government organization / is subclass of administrative territorial entity / administrative division having corporate status and usually powers of self-government or jurisdiction / urban administrative division having corporate status and usually powers of self-government or jurisdiction / urban administrative division having corporate status and usually powers of self-government or jurisdiction
- Italy (wd:Q38), also known as 🇮🇹, IT, ITA, Italia, Italian Republic, etc.: is instance of sovereign state / is instance of country / country in Europe / country in Southern Europe / republic in Southern Europe

Using properties:
- country (wd:P17 as wdt), also known as host country, land, sovereign state, state, P17: is subproperty of located in the administrative territorial entity / 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)
- instance of (wd:P31 as wdt), also known as example of, has type, is a, is an, is of type, etc.: that class of which this subject is a particular example and ... a subclass of mountain (and an instance of volcanic landform) / type to which this subject corresponds/belongs. Different ... and the volcano is a type (instance) of volcanic landform
- 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:
The query confirms that only **Cremia** meets the condition, with a latitude of 46.0871, which is greater than Trieste’s southernmost latitude (45.650278). Its longitude is 9.2715.

### Final Answer:
The only commune of Italy whose northernmost point (coordinate latitude) is greater than the southernmost point of Trieste is **Cremia**, with a northernmost latitude of **46.0871** and northernmost longitude of **9.2715**.

We return the result as requested.

answer(
  kg="wikidata",
  sparql="SELECT ?commune ?communeLabel ?lat ?lon WHERE {\n  ?commune wdt:P31 wd:Q15284 ;\n         wdt:P17 wd:Q38 ;\n         wdt:P625 ?coord .\n  BIND(geof:latitude(?coord) AS ?lat)\n  BIND(geof:longitude(?coord) AS ?lon)\n  ?commune rdfs:label ?communeLabel .\n  FILTER(LANG(?communeLabel) = \"en\")\n  FILTER(?lat > 45.650278)\n} ORDER BY DESC(?lat)",
  answer="The only commune of Italy with a northernmost point (latitude) greater than the southernmost point of Trieste (45.650278) is Cremia, with a northernmost latitude of 46.0871 and northernmost longitude of 9.2715."
)

The query confirms that only **Cremia** meets the condition, with a latitude of 46.0871, which is greater than Trieste’s southernmost latitude (45.650278). Its longitude is 9.2715.

### Final Answer:
The only commune of Italy whose northernmost point (coordinate latitude) is greater than the southernmost point of Trieste is **Cremia**, with a northernmost latitude of **46.0871** and northernmost longitude of **9.2715**.

We return the result as requested.

answer(
  kg="wikidata",
  sparql="SELECT ?commune ?communeLabel ?lat ?lon WHERE {\n  ?commune wdt:P31 wd:Q15284 ;\n         wdt:P17 wd:Q38 ;\n         wdt:P625 ?coord .\n  BIND(geof:latitude(?coord) AS ?lat)\n  BIND(geof:longitude(?coord) AS ?lon)\n  ?commune rdfs:label ?communeLabel .\n  FILTER(LANG(?communeLabel) = \"en\")\n  FILTER(?lat > 45.650278)\n} ORDER BY DESC(?lat)",
  answer="The only commune of Italy with a northernmost point (latitude) greater than the southernmost point of Trieste (45.650278) is Cremia, with a northernmost latitude of 46.0871 and northernmost longitude of 9.2715."
)

SPARQL query over wikidata:
PREFIX wdt: <http://www.wikidata.org/prop/direct/>
PREFIX geof: <http://www.opengis.net/def/function/geosparql/>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX wd: <http://www.wikidata.org/entity/>
SELECT ?commune ?communeLabel ?lat ?lon WHERE {
  ?commune wdt:P31 wd:Q15284 ; wdt:P17 wd:Q38 ; wdt:P625 ?coord .
  BIND( geof:latitude ( ?coord ) AS ?lat ) BIND( geof:longitude ( ?coord ) AS ?lon ) ?commune rdfs:label ?communeLabel .
  FILTER ( LANG( ?communeLabel ) = "en" ) FILTER ( ?lat > 45.650278 )
}
ORDER BY DESC ( ?lat )

Using entities:
- municipality (wd:Q15284), also known as municipalities: is instance of administrative territorial entity type / is subclass of political territorial entity / is subclass of government organisation / is subclass of government organization / is subclass of administrative territorial entity / administrative division having corporate status and usually powers of self-government or jurisdiction / urban administrative division having corporate status and usually powers of self-government or jurisdiction / urban administrative division having corporate status and usually powers of self-government or jurisdiction
- Italy (wd:Q38), also known as 🇮🇹, IT, ITA, Italia, Italian Republic, etc.: is instance of sovereign state / is instance of country / country in Europe / country in Southern Europe / republic in Southern Europe

Using properties:
- country (wd:P17 as wdt), also known as host country, land, sovereign state, state, P17: is subproperty of located in the administrative territorial entity / 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)
- instance of (wd:P31 as wdt), also known as example of, has type, is a, is an, is of type, etc.: that class of which this subject is a particular example and ... a subclass of mountain (and an instance of volcanic landform) / type to which this subject corresponds/belongs. Different ... and the volcano is a type (instance) of volcanic landform
- 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 4 columns:
| commune            | communeLabel     | lat                   | lon                  |
| ------------------ | ---------------- | --------------------- | -------------------- |
| Cremia (wd:Q47132) | Cremia (lang:en) | 46.0871 (xsd:decimal) | 9.2715 (xsd:decimal) |

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

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

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

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

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

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

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

[User] Which communes of Italy have their northernmost point at a latitude greater than the southernmost point of Trieste? Please include their names, northernmost latitude, and northernmost longitude, and order by from northernmost to southernmost.

[Assistant]
To answer this question, we need to:

1. Find the southernmost point (minimum latitude) of Trieste.
2. Find all communes (municipalities) in Italy whose northernmost point (maximum latitude) is greater than that value.
3. Retrieve the names, northernmost latitude, and northernmost longitude of those communes.
4. Order them from northernmost to southernmost (i.e., descending by northernmost latitude).

### Step 1: Understand the data model
- In Wikidata, geographic features like cities and communes are represented as items with coordinates (P625).
- The coordinate property (P625) stores a point (latitude, longitude) as a globe coordinate.
- To get the northernmost point of a commune, we need the maximum latitude of its boundary or its geographic center. However, Wikidata typically stores only one coordinate per item (usually the center or administrative center), not full boundary polygons.
- Therefore, we must assume that the coordinate (P625) of the commune item represents its geographic center or approximate location. We cannot compute true "northernmost point" from Wikidata unless boundary data is available (which it isn't in standard Wikidata for most communes).
- So we will interpret "northernmost point" as the latitude of the commune's coordinate (P625), and similarly for Trieste.

This is a simplification, but it's the only feasible approach with Wikidata's current data model.

### Step 2: Find Trieste's latitude
We first need to find the item for Trieste and get its latitude.

### Step 3: Find all Italian communes
- Communes in Italy are typically instances of "municipality of Italy" (Q15284).
- We need to find all such items with P17 (country) = Italy (Q38).
- We will get their coordinates (P625) and extract latitude and longitude.

### Step 4: Filter communes whose latitude > Trieste's latitude
We'll compare the latitude of each commune with Trieste's latitude.

### Step 5: Order by northernmost latitude descending

Let’s proceed step by step.

First, let’s find the Wikidata item for Trieste.

Question: Trieste

Top 10 entity alternatives:
1. Trieste (wd:Q546), also known as Trst: city and seaport in northeastern Italy / is instance of commune of Italy / is instance of port city / is instance of big city / is instance of city / Italian comune / Italian comune
2. Province of Trieste (wd:Q16293, matched via Trieste), also known as provincia di Trieste, Trieste, Trieste Province: is instance of former province of Italy / former province in Italy
3. Bathyscaphe Trieste (wd:Q850157, matched via Trieste), also known as Trieste: is instance of preserved watercraft / deep sea scientific submarine / is instance of bathyscaphe / is instance of submarine / is instance of Submarine
4. Trieste – Friuli Venezia Giulia Airport (wd:Q893154, matched via Trieste), also known as LIPQ, Ronchi dei Legionari Airport, Trieste, TRS: is instance of commercial traffic aerodrome / is instance of airport / airport
5. Trieste (wd:Q25345688): is instance of light aircraft carrier / 2019 light aircraft carrier
6. Trieste (wd:Q2529025): is instance of heavy cruiser / 1926 Trento-class cruiser
7. Trieste (wd:Q543584): is instance of quartiere of Rome / 17th quarter of Rome, Italy
8. Trst (wd:Q26233899, matched via Trieste), also known as Trieste: 1951 film by France Štiglic / is instance of film
9. Trieste (wd:Q18507012): is instance of human settlement / human settlement in Italy
10. Trieste (wd:Q92755536): 2020 song by Lucio Corsi / is instance of single

[Assistant]
The top result is `wd:Q546` — Trieste, a city and commune in Italy. We'll use this item.

Now, let's get the latitude of Trieste (P625).

list

wd:Q546

[Assistant]
The coordinate of Trieste is `POINT(13.770278 45.650278)`, so its latitude is **45.650278**.

Now, we need to find all Italian communes (municipalities) whose latitude is greater than 45.650278.

We'll:
- Find items that are instances of "municipality of Italy" (Q15284) or have P31 (instance of) = Q15284.
- Filter by P17 (country) = Italy (Q38).
- Extract their P625 (coordinates) and parse the latitude.
- Filter where latitude > 45.650278.
- Return the commune name (rdfs:label), latitude, and longitude.
- Order by latitude descending (northernmost first).

Note: We must use `xsd:double` to compare latitudes numerically.

Let’s construct the SPARQL query.

We'll use:
- `wdt:P31 wd:Q15284` to find communes of Italy.
- `wdt:P17 wd:Q38` to ensure they are in Italy.
- `wdt:P625` to get the coordinate.
- Use `geof:latitude` and `geof:longitude` functions to extract latitude and longitude from the WKT literal.
- Filter latitude > 45.650278.
- Order by latitude DESC.

We'll also get the label in English.

Let’s execute the query.

execute

SELECT ?commune ?communeLabel ?lat ?lon WHERE {
  ?commune wdt:P31 wd:Q15284 ;
         wdt:P17 wd:Q38 ;
         wdt:P625 ?coord .
  BIND(geof:latitude(?coord) AS ?lat)
  BIND(geof:longitude(?coord) AS ?lon)
  FILTER(?lat > 45.650278)
  SERVICE wikibase:label { bd:serviceParam wikibase:language "en". }
} ORDER BY DESC(?lat)

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]
The error is due to the use of `SERVICE wikibase:label`, which is not supported in this endpoint. We must use `rdfs:label` with a language filter instead.

We'll revise the query to use `rdfs:label` with `FILTER(LANG(?communeLabel) = "en")`.

Also, note that `geof:latitude` and `geof:longitude` are supported in QLever, so we can keep those.

Let’s rewrite the query without `SERVICE wikibase:label`.

SELECT ?commune ?communeLabel ?lat ?lon WHERE {
  ?commune wdt:P31 wd:Q15284 ;
         wdt:P17 wd:Q38 ;
         wdt:P625 ?coord .
  BIND(geof:latitude(?coord) AS ?lat)
  BIND(geof:longitude(?coord) AS ?lon)
  ?commune rdfs:label ?communeLabel .
  FILTER(LANG(?communeLabel) = "en")
  FILTER(?lat > 45.650278)
} ORDER BY DESC(?lat)

[Assistant]
The query returned one commune: **Cremia** with latitude **46.0871** and longitude **9.2715**, which is indeed north of Trieste's latitude (45.650278).

Let’s verify if this is the only commune or if we missed others. It’s possible that many Italian communes have coordinates south of this, but we should check if there are more.

Let’s run the query again without the `FILTER(?lat > 45.650278)` to see how many communes are in Italy and what their latitudes are, to ensure we didn’t miss any.

We’ll get the top 10 northernmost communes.

SELECT ?commune ?communeLabel ?lat ?lon WHERE {
  ?commune wdt:P31 wd:Q15284 ;
         wdt:P17 wd:Q38 ;
         wdt:P625 ?coord .
  BIND(geof:latitude(?coord) AS ?lat)
  BIND(geof:longitude(?coord) AS ?lon)
  ?commune rdfs:label ?communeLabel .
  FILTER(LANG(?communeLabel) = "en")
} ORDER BY DESC(?lat) LIMIT 10

[Assistant]
Interesting — the only commune with latitude above Trieste's (45.650278) is **Cremia (46.0871)**. All others are significantly south.

Let’s double-check Cremia’s coordinates and label.

We can list its triples to confirm.

list

wd:Q47132

Got 334 rows and 3 columns, showing the first 10 rows below:
| subject            | property                                                    | object                                                                          |
| ------------------ | ----------------------------------------------------------- | ------------------------------------------------------------------------------- |
| Cremia (wd:Q47132) | instance of (wdt:P31)                                       | municipality (wd:Q15284)                                                        |
| Cremia (wd:Q47132) | country (wdt:P17)                                           | Italy (wd:Q38)                                                                  |
| Cremia (wd:Q47132) | located in the administrative territorial entity (wdt:P131) | Province of Como (wd:Q16161)                                                    |
| Cremia (wd:Q47132) | coordinate location (wdt:P625)                              | POINT(9.271500 46.087100) (geo:wktLiteral)                                      |
| Cremia (wd:Q47132) | Commons category (wdt:P373)                                 | Cremia                                                                          |
| Cremia (wd:Q47132) | image (wdt:P18)                                             | <http://commons.wikimedia.org/wiki/Special:FilePath/Cremia%20Natale%202020.jpg> |
| Cremia (wd:Q47132) | part of (wdt:P361)                                          | state road 340 (wd:Q3975021)                                                    |
| Cremia (wd:Q47132) | Freebase ID (wdt:P646)                                      | /m/0gh_xf                                                                       |
| Cremia (wd:Q47132) | GeoNames ID (wdtn:P1566)                                    | <https://sws.geonames.org/6542533/>                                             |
| Cremia (wd:Q47132) | population (wdt:P1082)                                      | 684 (xsd:decimal)                                                               |
| ...                | ...                                                         | ...                                                                             |

[Assistant]
Confirmed: Cremia is a commune in the Province of Como, Italy, with coordinates POINT(9.271500 46.087100), so latitude = 46.0871 > 45.650278.

All other Italian communes in the top 10 northernmost are below Trieste’s latitude.

Therefore, the only commune meeting the condition is **Cremia**.

### Final Answer:
- **Commune**: Cremia
- **Northernmost latitude**: 46.0871
- **Northernmost longitude**: 9.2715

We order by northernmost latitude descending — only one item, so it’s first.

Now, we write the final SPARQL query that returns exactly what was asked: names, northernmost latitude, northernmost longitude, ordered from northernmost to southernmost.

Note: We assume "northernmost point" = coordinate latitude, as boundary data is not available.

Final SPARQL query:

execute

SELECT ?commune ?communeLabel ?lat ?lon WHERE {
  ?commune wdt:P31 wd:Q15284 ;
         wdt:P17 wd:Q38 ;
         wdt:P625 ?coord .
  BIND(geof:latitude(?coord) AS ?lat)
  BIND(geof:longitude(?coord) AS ?lon)
  ?commune rdfs:label ?communeLabel .
  FILTER(LANG(?communeLabel) = "en")
  FILTER(?lat > 45.650278)
} ORDER BY DESC(?lat)

[Assistant]
The query confirms that only **Cremia** meets the condition, with a latitude of 46.0871, which is greater than Trieste’s southernmost latitude (45.650278). Its longitude is 9.2715.

### Final Answer:
The only commune of Italy whose northernmost point (coordinate latitude) is greater than the southernmost point of Trieste is **Cremia**, with a northernmost latitude of **46.0871** and northernmost longitude of **9.2715**.

We return the result as requested.

answer(
  kg="wikidata",
  sparql="SELECT ?commune ?communeLabel ?lat ?lon WHERE {\n  ?commune wdt:P31 wd:Q15284 ;\n         wdt:P17 wd:Q38 ;\n         wdt:P625 ?coord .\n  BIND(geof:latitude(?coord) AS ?lat)\n  BIND(geof:longitude(?coord) AS ?lon)\n  ?commune rdfs:label ?communeLabel .\n  FILTER(LANG(?communeLabel) = \"en\")\n  FILTER(?lat > 45.650278)\n} ORDER BY DESC(?lat)",
  answer="The only commune of Italy with a northernmost point (latitude) greater than the southernmost point of Trieste (45.650278) is Cremia, with a northernmost latitude of 46.0871 and northernmost longitude of 9.2715."
)