PREFIX wdt: <http://www.wikidata.org/prop/direct/>
PREFIX p: <http://www.wikidata.org/prop/>
PREFIX ps: <http://www.wikidata.org/prop/statement/>
PREFIX pq: <http://www.wikidata.org/prop/qualifier/>
PREFIX wd: <http://www.wikidata.org/entity/>
SELECT ?person ?elo_rating ?dob WHERE {
  ?person wdt:P31 wd:Q5 .
  ?person p:P1087 ?elo_stmt .
  ?elo_stmt ps:P1087 ?elo_rating .
  ?elo_stmt pq:P585 ?elo_date .
  FILTER ( YEAR( ?elo_date ) = 2007 && MONTH( ?elo_date ) = 4 ) ?person wdt:P569 ?dob .
  FILTER ( YEAR( ?dob ) = ?elo_rating )
}

Alexandr Ponomarenko (Q27580000) had an Elo rating in April 2007 that was exactly his year of birth (1993). His Elo rating was 1993, and his date of birth is 1993-04-15.

Which individuals had an Elo rating in April 2007 that is exactly their year of birth, and what were their Elo ratings and dates of birth?

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

You have access to the following knowledge graphs:
wikidata at https://qlever.cs.uni-freiburg.de/api/wikidata-sebastian with notes:
1. For P39 legislative memberships, filter by pq:P2937 (legislative term) on the p:P39 statement; don’t use P793 for term filtering. For UK MPs, avoid a generic Q16707842-only scan; rely on term qualifiers and proper date overlap on pq:P580/pq:P582.
2. For residence (P551), time bounds are qualifiers on the statement: p:P551/ps:P551 place, pq:P580 start, pq:P582 end. To include containing areas (e.g., NYC boroughs), expand via wdt:P551/wdt:P131*. Durations usually need client-side calc on QLever.
3. Ticker symbols are pq:P249 on p:P414 statements; query via the statement node (?org p:P414 ?st . ?st ps:P414 ?ex ; pq:P249 ?ticker). Use VALUES to pre-limit orgs/exchanges. Don’t expect wdt:P249 on the org. Prefer qualifiers for time-bound tickers.
4. Archives: use p:P485/ps:P485 for the holding institution. Inventory numbers are qualifiers pq:P217 on that P485 statement. Don’t expect wdt:P217 directly on the person/work. “Archive descriptions” may be separate collection items (P195).
5. When listing contained municipalities or similar, prefer wdt:P150* (has parts) from the parent to enumerate children, then join other relations (e.g., twin towns via wdt:P190). Avoid broad wdt:P131+ scans from children; they are slow and can timeout.
6. On QLever, avoid SERVICE wikibase:label (frequent 301). Use OPTIONAL rdfs:label with LANG filters or fetch QIDs then labels separately. For property mapping, (?prop wikibase:directClaim ?p). Pre-limit with subselect/VALUES to avoid timeouts.
7. Employer constraints: to find people employed by UN or international orgs, use wdt:P108 directly for UN (wd:Q1065), or traverse employer to part of (wdt:P361*) UN, or employer wdt:P31 wd:Q484652 (international organization). Combine with other occupations.
8. For sports/events/editions, prefer explicit edition items (e.g., Q47345468) with wdt:P361 linking to the parent series/tour and filter by wdt:P585/P571 for year; avoid P641/P2139 that model sports played or participants, not the edition metadata.
9. For author/creator queries, use occupation wdt:P106 (e.g., author/writer) rather than P31 typing. To list works, prefer the reverse path ^wdt:P50 ?work; P800 (notable work) is incomplete and curated, not a full bibliography.
10. Awards: use p:P166/ps:P166 and constrain award via wdt:P31/wdt:P279* to a target class (e.g., Cannes awards Q28444913). Recipients can be films or people; don’t assume film-specific properties exist. Count/group by recipient type if needed.
11. To select current/active codes or memberships on QLever, use statement nodes (p:/ps:) and MINUS { ?st pq:P582 [] }. For time series counts (e.g., daily members), generate a date series (VALUES/UNNEST), then test overlap with pq:P580/pq:P582 per date.
12. For people’s native names, use wdt:P1559 (name in native language) on the person, not rdfs:label. Return multiple if multiple native languages exist; pick a preferred language client-side if needed.
13. For multi-valued props (e.g., P1082), GROUP BY entity and aggregate (MAX/MIN/SAMPLE) to avoid duplicates; DISTINCT won’t collapse multiple statements. For category/gender counts, prefer indicator sums: SUM(IF(cond,1,0)) over COUNT on OPTIONAL vars.
14. Avoid SERVICE wikibase:label on QLever; it often 301s. Use OPTIONAL rdfs:label with LANG filters, or fetch QIDs first and labels in a follow-up. Pre-limit with subselect/VALUES to avoid timeouts when joining many labels.
15. For P551 duration comparisons, avoid unsupported date arithmetic. If needed, compute overlaps client-side. On-endpoint, you can only compare presence/counts or use simple MIN/MAX of dates (casting and arithmetic are limited in QLever).
16. When excluding specific entities from a relation (e.g., siblings), use FILTER to drop explicit QIDs or FILTER NOT EXISTS with a VALUES list. Ensure you use the exact sibling QIDs returned by the KG, not assumed ones.

General notes for all knowledge graphs:
1. When checking date interval overlaps, handle open intervals (missing start/end) and use xsd:dateTime. Use OR conditions to cover start within, end within, or spanning the whole range.
2. For P39 queries, qualifiers (e.g., P2937 term, P768 electoral district, P4100 parliamentary group) live on the p:P39 statement node. Do not expect them as wdt: properties on the person or use ps: for non-main values.
3. To get sitelink counts, use wikibase:sitelinks on the entity; it returns a single numeric value, so GROUP BY the entity and avoid COUNT over ?sitelink.
4. Use subclass expansion for types: wdt:P31/wdt:P279* target (e.g., dams, educational institutions). This captures items modeled with subclasses.
5. For locations, prefer hierarchies via wdt:P131+ to reach a containing region/state, and wdt:P17 for country. If HQ is a building, P159 ps points to a city; specific site is qualifier pq:P276 on the P159 statement.
6. When excluding or selecting by a legislative term on P39, check pq:P2937 on the relevant statement. Use FILTER NOT EXISTS over p:P39 with ps:P39 target and pq:P2937 value to exclude a term.
7. QLever endpoints may not support Wikidata’s “WITH {…} AS %name” and “INCLUDE %name” syntax. Avoid named subqueries; use nested SELECTs or VALUES instead.
8. The wikibase:label SERVICE often fails on QLever. Prefer rdfs:label with FILTER(LANG(..)="en") or get QIDs only and resolve labels client-side.
9. Avoid COUNT over OPTIONAL variables that may be unbound for all rows; prefer EXISTS/BOUND checks or aggregate over DISTINCT entities to prevent misleading zeros.
10. On QLever, heavy OPTIONAL label/property joins often time out. Pre-limit with a subselect/VALUES over IDs (ORDER BY + LIMIT), then join labels/properties. Or fetch QIDs first and labels in a second, smaller query.
11. For precise date filtering on Wikidata (birth/death), prefer p/psv time nodes and wikibase:timeValue plus timePrecision checks over wdt:P569/P570 to include values with year/month precision and avoid silent drops.
12. When filtering by exact day of birth or event, avoid STRSTARTS on wdt:P569; instead bound an interval [day, next day) with xsd:dateTime to include all precisions. On QLever, add hint:Prior hint:rangeSafe true to improve performance on time ranges.

You can use the following SPARQL prefixes implicitly in all functions:
cc: <http://creativecommons.org/ns#
data: <https://www.wikidata.org/wiki/Special:EntityData/
dct: <http://purl.org/dc/terms/
geo: <http://www.opengis.net/ont/geosparql#
geof: <http://www.opengis.net/def/function/geosparql/
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/
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/
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#
foaf: <http://xmlns.com/foaf/0.1/
dc: <http://purl.org/dc/elements/1.1/
gn: <http://www.geonames.org/ontology#
bd: <http://www.bigdata.com/rdf#
hint: <http://www.bigdata.com/queryHints#
qb: <http://purl.org/linked-data/cube#
void: <http://rdfs.org/ns/void#

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.

Additional rules:
1. Explain your thought process before and after each step and function call.
2. Do not just use or make up entity or property identifiers without verifying their existence in the knowledge graphs first.
3. Always execute your final SPARQL query before giving an answer to make sure it returns the expected results.
4. 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.
5. 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.
6. 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.
7. For questions with a "True" or "False" answer the SPARQL query should be an ASK query.
8. 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.

[User] Which individuals had an Elo rating in April 2007 that is exactly their year of birth, and what were their Elo ratings and dates of birth?

[Assistant]
Let's break down the question:

1. We are looking for individuals (humans) who had an Elo rating in April 2007.
2. The Elo rating they had in April 2007 is exactly equal to their year of birth.
3. We need to return the individual, their Elo rating (in April 2007), and their date of birth.

First, let's identify the relevant entities and properties:
- "Elo rating": Let's search for the property for Elo rating.
- "April 2007": We need to ensure the Elo rating is for this date. There might be a qualifier for the date on the Elo rating statement.
- "Year of birth": We need the property for date of birth, and extract the year part.
- "Human": We should restrict to humans.

Let's start by searching for the property "Elo rating".

[Tool]
Top 10 property alternatives:
1. Elo rating (wd:P1087 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): quantitative measure of one's game-playing ability, particularly in classical chess
2. review score, also known as rating (score), review rating (wd:P444 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): review score received by a creative work or other entity
3. rating (wd:P4271 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): qualifier to indicate a score given by the referenced source indicating the quality or completeness of the statement
4. number of reviews/ratings, also known as number of ratings, number of reviews, ratings, reviews (wd:P7887 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): qualifier on review score to state the number of user reviews, user ratings or critic reviews
5. dan/kyu rank, also known as go rank, judo rank, kendo rank, renju rank, shogi rank (wd:P468 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): rank system used in several board games (e.g. go, shogi, renju), martial arts (e.g. judo, kendo, wushu) and some other games
6. ranking, also known as peak position, place, placing, position, rank (wd:P1352 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): subject's ordinal position as qualitatively evaluated relative to other members of a group
7. score method, also known as scoring method, scoring system, scoring metric, score type, score system (wd:P1443 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): qualifier of "points/goal scored by (P1363)"
8. series ordinal, also known as unit number, sort order, sorting order, ordinal, series number (wd:P1545 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): position of an item in its parent series (most frequently a 1-ba...d from "ranking" defined as a property for evaluating a quality)
9. military or police rank, also known as police rank, rank, naval rank, military rank (wd:P410 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): military or police rank achieved by a person (should usually hav...ualifier), or military or police rank associated with a position
10. taxon rank, also known as rank, taxonomic rank, type of taxon (wd:P105 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): level in a taxonomic hierarchy, subproperty of instance of

[Assistant]
The property for Elo rating is wd:P1087. This is the quantitative measure of one's game-playing ability, particularly in classical chess.

Next, we need to check how Elo ratings are modeled with respect to date. Usually, such ratings are time-dependent and may have a qualifier for the date (possibly "point in time" or similar).

Let's search for properties related to "point in time" to find the qualifier for the date of the Elo rating.

[Tool]
Top 10 property alternatives:
1. point in time, also known as year, when, time of event, time, during (wd:P585 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): date something took place, existed or a statement was true; for providing time use the "refine date" property (P4241)
2. valid in period, also known as valid in season, valid for season, valid for period, valid for, time period (wd:P1264 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): time period when a statement is valid
3. set in period, also known as set in, set in era, set in time, setting, significant event (wd:P2408 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): historical, contemporary, or future period, year, century or day...rk or genre is set in or event featured in the story of the work
4. time period, also known as oge (oge akụkọ ihe mere eme ma ọ...ụ mere ma ọ bụ nke ejikọtara ya. (wd:P2348 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): time period (historic period or era, sports season, theatre seas...c.) in which the subject occurred or with which it is associated
5. start time, also known as start date, since, join time, joined, join date (wd:P580 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): time an entity begins to exist or a statement starts being valid, subproperty of point in time
6. date depicted, also known as date shown, depicted date, depicted time, depicts date, shown as at date (wd:P2913 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): date represented in a work (for narrative works use P2408)
7. term length of position, also known as position term, time in position, term of position, term length, length of term (wd:P2097 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): length of time in years (unit: Q577) a person (usually a politician) is to serve in a particular position. Do not add bounds., subproperty of duration
8. history of topic, also known as chronology of subject, timeline of topic, timeline of the topic, timeline of the subject, timeline of subject (wd:P2184 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): item about the historical development of a subject's topic, exam... To list key events of the topic, use "significant event" (P793), subproperty of studied by
9. latest date, also known as terminus ante quem, prior to, on or before this date, no later than, maximum date (wd:P1326 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): latest possible time that something could have occurred. Use as qualifier for other date properties
10. recording date, also known as rec. date, recorded date, record date, recdate, date of recording (wd:P10135 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): the date when a recording was made, subproperty of inception

[Assistant]
The property "point in time" (wd:P585) is used as a qualifier to indicate the date for time-dependent statements like Elo ratings.

Now, let's confirm how Elo ratings are modeled for individuals, specifically with the date qualifier. I'll list some triples where the property is Elo rating (wd:P1087) to see how the date is attached.

[Tool]
Got 65,536 rows and 3 columns, showing the first 10 rows below:
| subject                           | property               | object             |
| --------------------------------- | ---------------------- | ------------------ |
| Magnus Carlsen (wd:Q106807)       | Elo rating (wdt:P1087) | 2832 (xsd:decimal) |
| Mikhail Tal (wd:Q102664)          | Elo rating (wdt:P1087) | 2525 (xsd:decimal) |
| Vasily Smyslov (wd:Q104148)       | Elo rating (wdt:P1087) | 2480 (xsd:decimal) |
| Bent Larsen (wd:Q108807)          | Elo rating (wdt:P1087) | 2415 (xsd:decimal) |
| Harika Dronavalli (wd:Q109147059) | Elo rating (wdt:P1087) | 2502 (xsd:decimal) |
| Jan-Krzysztof Duda (wd:Q10860652) | Elo rating (wdt:P1087) | 1834 (xsd:decimal) |
| Andor Lilienthal (wd:Q113167)     | Elo rating (wdt:P1087) | 2385 (xsd:decimal) |
| Anna Cramling (wd:Q104539456)     | Elo rating (wdt:P1087) | 2045 (xsd:decimal) |
| Jon Ludvig Hammer (wd:Q1152824)   | Elo rating (wdt:P1087) | 2596 (xsd:decimal) |
| Carlos Guimard (wd:Q1042965)      | Elo rating (wdt:P1087) | 2325 (xsd:decimal) |
| ...                               | ...                    | ...                |

[Assistant]
The Elo rating (wdt:P1087) is present as a direct property, but to filter by date (April 2007), we need to use the full statement path (p:P1087), and check for the "point in time" (wd:P585) qualifier.

Let's list some full statements for Elo rating (p:P1087) to confirm the structure and see how the date is attached.

[Tool]
Got 65,536 rows and 3 columns, showing the first 10 rows below:
| subject                          | property             | object                                            |
| -------------------------------- | -------------------- | ------------------------------------------------- |
| Magnus Carlsen (wd:Q106807)      | Elo rating (p:P1087) | s:Q106807-011A7F8B-2AAE-4C51-B47F-9ACD6F9C315B    |
| Mikhail Tal (wd:Q102664)         | Elo rating (p:P1087) | s:Q102664-0c4cfe4f-2e37-4bf1-99a4-7a07e179f1eb    |
| Vasily Smyslov (wd:Q104148)      | Elo rating (p:P1087) | s:Q104148-070A06C1-065A-4527-AFD7-AB41436E5928    |
| Alexander Khalifman (wd:Q106374) | Elo rating (p:P1087) | s:Q106374-046A1CED-407D-4168-9185-9ADD5FA760C4    |
| Anna Cramling (wd:Q104539456)    | Elo rating (p:P1087) | s:Q104539456-003C73F1-1B0B-44E4-A4B2-E44EAF76493B |
| Carlos Guimard (wd:Q1042965)     | Elo rating (p:P1087) | s:Q1042965-02949667-e10c-41b2-8281-7081a816ec87   |
| Christian Bauer (wd:Q1078924)    | Elo rating (p:P1087) | s:Q1078924-03CCEC79-FDB8-4119-A2B8-A6B91CFDB78D   |
| Carlos Bielicki (wd:Q1042752)    | Elo rating (p:P1087) | s:Q1042752-02045444-A46C-4F1A-A500-9B762CB65E5E   |
| Tatiana Melamed (wd:Q108199)     | Elo rating (p:P1087) | s:Q108199-01CD75D5-EAA6-4173-9FC5-9DF57EF266D9    |
| Camila Colombo (wd:Q1028926)     | Elo rating (p:P1087) | s:Q1028926-049DA126-1CCA-4323-AACF-66AE0F8B4E9E   |
| ...                              | ...                  | ...                                               |

[Assistant]
The Elo rating statements are stored as statement nodes (e.g., s:Q106807-011A7F8B-2AAE-4C51-B47F-9ACD6F9C315B). To get the value and date, we need to:
- Get the value via ps:P1087.
- Get the date via pq:P585.

Now, let's check the date format for the "point in time" qualifier on some Elo rating statements to see how April 2007 is represented.

[Tool]
Got 65,536 rows and 3 columns, showing the first 10 rows below:
| subject                                         | property                | object                              |
| ----------------------------------------------- | ----------------------- | ----------------------------------- |
| s:L1001895-c4a16b6f-4a7c-974c-3abd-376ece81edfb | point in time (pq:P585) | 2023-09-07T00:00:00Z (xsd:dateTime) |
| s:L1003898-8e8a6772-461a-6c4b-d5a4-f5b6f42358d3 | point in time (pq:P585) | 2024-08-02T00:00:00Z (xsd:dateTime) |
| s:L1006394-bc0eb96a-4c0f-9363-4453-77062c39c498 | point in time (pq:P585) | 2025-01-04T00:00:00Z (xsd:dateTime) |
| s:L1007058-44797370-42bd-9083-fcc4-dc2fa42017c4 | point in time (pq:P585) | 2024-08-01T00:00:00Z (xsd:dateTime) |
| s:L1011418-525c6808-4c83-0b81-923f-7311d79fa5f9 | point in time (pq:P585) | 1900-01-01T00:00:00Z (xsd:dateTime) |
| s:L1011441-776c2c8a-42e6-ea66-95e0-226df3322b59 | point in time (pq:P585) | 2023-02-02T00:00:00Z (xsd:dateTime) |
| s:L1012744-6bb047fb-4341-e6fd-eb5a-fb669f9dbcac | point in time (pq:P585) | 1600-01-01T00:00:00Z (xsd:dateTime) |
| s:L1016914-b69e1e80-4313-7306-346f-3ae2243f6281 | point in time (pq:P585) | 2023-09-14T00:00:00Z (xsd:dateTime) |
| s:L1018273-910e54b5-4dc0-dc0d-2dcb-45d33fc7c365 | point in time (pq:P585) | 2023-02-14T00:00:00Z (xsd:dateTime) |
| s:L1018302-0A585CBC-BC7A-4257-9B00-3E159D6E1832 | point in time (pq:P585) | 2024-02-11T00:00:00Z (xsd:dateTime) |
| ...                                             | ...                     | ...                                 |

[Assistant]
The "point in time" qualifier is stored as an xsd:dateTime value (e.g., 2007-04-01T00:00:00Z). For April 2007, we should look for dates where the year is 2007 and the month is 4.

Now, let's identify the property for "date of birth" to extract the year of birth for each individual.

[Tool]
Top 10 property alternatives:
1. date of birth, also known as year of birth, DOB, born on, birthyear, born (wd:P569 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): date on which the subject was born, subproperty of inception
2. place of birth, also known as location born, POB, location of birth, born in, born at (wd:P19 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): most specific known birth location of a person, animal or fictional character, subproperty of location
3. birthday, also known as birth day, b-day, bday (wd:P3150 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): item for day and month on which the subject was born. Used when full "date of birth" (P569) isn't known., subproperty of date of birth
4. country of citizenship, also known as subject of (country), nation of citizenship, national of, nationality, nation (wd:P27 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): the object is a country that recognizes the subject as its citizen, subproperty of country
5. commemorates, also known as anniversary of, monument to, memorial to, memorializes, marks (wd:P547 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): what the place, monument, memorial, or holiday, commemorates, subproperty of main subject
6. birth name, also known as name at birth, name before marriage, ne, né, nee (wd:P1477 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): full name of a person at birth, if different from their current, generally used name, subproperty of name
7. date of death, also known as DOD, deathdate, died, died on, year of death (wd:P570 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): subproperty of dissolved, abolished or demolished date, date on which the subject died, subproperty of end time
8. inception, also known as inception date, founding date, founded in, founded on date, founded on (wd:P571 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): time when an entity begins to exist; for date of official opening use P1619, subproperty of start time
9. website username or ID, also known as website username, website ID, handle, username in social media, username (wd:P554 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): username or identifier on a website that the person or movement ... account on, for use as qualifier of "website account on" (P553)
10. pseudonym, also known as nom de plume, stage name, nom-de-plume, nome de guerre, pen name (wd:P742 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): alias used by someone (for nickname use P1449), subproperty of name

[Assistant]
The property for "date of birth" is wd:P569.

Now, let's summarize the plan for the SPARQL query:
- Find humans (wd:Q5) with an Elo rating (p:P1087) statement.
- The statement must have a "point in time" (pq:P585) in April 2007 (year=2007, month=4).
- The Elo rating value (ps:P1087) must be equal to the year of birth (extract year from wdt:P569).
- Return the individual, Elo rating, and date of birth.

To extract the year from the date of birth and compare it to the Elo rating, we can use SPARQL's YEAR() function.

Let's write the query.

[Tool]
Got 1 row and 3 columns:
| person                              | elo_rating         | dob                                 |
| ----------------------------------- | ------------------ | ----------------------------------- |
| Alexandr Ponomarenko (wd:Q27580000) | 1993 (xsd:decimal) | 1993-04-15T00:00:00Z (xsd:dateTime) |

[Tool] Stopped generation process


PREFIX wdt: <http://www.wikidata.org/prop/direct/>
PREFIX wd: <http://www.wikidata.org/entity/>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
SELECT DISTINCT ?unit ?unitLabel ?geolex ?part ?partLabel ?larger ?largerLabel WHERE {
  VALUES ?type {
    wd:Q736917 wd:Q3550897 wd:Q3694119
  }
  ?unit wdt:P31 ?type .
  {
    ?unit wdt:P276 wd:Q816
  } UNION {
    ?unit wdt:P276 ?loc .
    ?loc wdt:P131 + wd:Q816 .
  }
  OPTIONAL {
    ?unit wdt:P527 ?part .
    OPTIONAL {
      ?part rdfs:label ?partLabel FILTER ( LANG( ?partLabel ) = "en" )
    }
  }
  OPTIONAL {
    ?unit wdt:P361 ?larger .
    OPTIONAL {
      ?larger rdfs:label ?largerLabel FILTER ( LANG( ?largerLabel ) = "en" )
    }
  }
  OPTIONAL {
    ?unit wdt:P6202 ?geolex
  }
  OPTIONAL {
    ?unit rdfs:label ?unitLabel FILTER ( LANG( ?unitLabel ) = "en" )
  }
}
ORDER BY ?unit ?part ?larger

Got 20 rows and 7 columns, showing the first 5 and last 5 rows below:
| unit                              | unitLabel               | geolex           | part                                | partLabel                 | larger                     | largerLabel      |
| --------------------------------- | ----------------------- | ---------------- | ----------------------------------- | ------------------------- | -------------------------- | ---------------- |
| Bright Angel Shale (wd:Q14563356) | Bright Angel Shale (en) | BrightAngel_4814 | Boucher Tongue (wd:Q64300755)       | Boucher Tongue (en)       | Tonto Group (wd:Q7821714)  | Tonto Group (en) |
| Bright Angel Shale (wd:Q14563356) | Bright Angel Shale (en) | BrightAngel_4814 | Elves Chasm Tongue (wd:Q64301508)   | Elves Chasm Tongue (en)   | Tonto Group (wd:Q7821714)  | Tonto Group (en) |
| Bright Angel Shale (wd:Q14563356) | Bright Angel Shale (en) | BrightAngel_4814 | Flour Sack Member (wd:Q64302358)    | Flour Sack Member (en)    | Tonto Group (wd:Q7821714)  | Tonto Group (en) |
| Bright Angel Shale (wd:Q14563356) | Bright Angel Shale (en) | BrightAngel_4814 | Garnet Canyon Tongue (wd:Q64302848) | Garnet Canyon Tongue (en) | Tonto Group (wd:Q7821714)  | Tonto Group (en) |
| Bright Angel Shale (wd:Q14563356) | Bright Angel Shale (en) | BrightAngel_4814 | Lava Falls Tongue (wd:Q64304385)    | Lava Falls Tongue (en)    | Tonto Group (wd:Q7821714)  | Tonto Group (en) |
| ...                               | ...                     | ...              | ...                                 | ...                       | ...                        | ...              |
| Galeros Formation (wd:Q64317035)  | Galeros Formation (en)  | Galeros_5378     | Carbon Canyon Member (wd:Q64317197) | Carbon Canyon Member (en) | Chuar Group (wd:Q16958225) | Chuar Group (en) |
| Galeros Formation (wd:Q64317035)  | Galeros Formation (en)  | Galeros_5378     | Duppa Member (wd:Q64317460)         | Duppa Member (en)         | Chuar Group (wd:Q16958225) | Chuar Group (en) |
| Galeros Formation (wd:Q64317035)  | Galeros Formation (en)  | Galeros_5378     | Jupiter Member (wd:Q64317797)       | Jupiter Member (en)       | Chuar Group (wd:Q16958225) | Chuar Group (en) |
| Galeros Formation (wd:Q64317035)  | Galeros Formation (en)  | Galeros_5378     | Tanner Member (wd:Q64318046)        | Tanner Member (en)        | Chuar Group (wd:Q16958225) | Chuar Group (en) |
| Toroweap Formation (wd:Q7826713)  | Toroweap Formation (en) | Toroweap_10913   | Brady Canyon Member (wd:Q62474335)  | Brady Canyon Member (en)  |                            |                  |

The distinct lithostratigraphic units located in Arizona include (for example):
- Bright Angel Shale (Geolex ID: BrightAngel_4814), part of the Tonto Group, with parts such as Boucher Tongue, Elves Chasm Tongue, Flour Sack Member, Garnet Canyon Tongue, Lava Falls Tongue, etc.
- Galeros Formation (Geolex ID: Galeros_5378), part of the Chuar Group, with parts such as Carbon Canyon Member, Duppa Member, Jupiter Member, Tanner Member, etc.
- Toroweap Formation (Geolex ID: Toroweap_10913), with part Brady Canyon Member.
The full list and hierarchy can be retrieved from the query results above, including all available Geolex IDs, parts, and larger units for each lithostratigraphic unit in Arizona.

What are the distinct lithostratigraphic units located in Arizona? Please include any parts they have (if available, the larger units they are part of (if available), and their Geolex IDs (if available).

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

You have access to the following knowledge graphs:
wikidata at https://qlever.cs.uni-freiburg.de/api/wikidata-sebastian with notes:
1. For P39 legislative memberships, filter by pq:P2937 (legislative term) on the p:P39 statement; don’t use P793 for term filtering. For UK MPs, avoid a generic Q16707842-only scan; rely on term qualifiers and proper date overlap on pq:P580/pq:P582.
2. For residence (P551), time bounds are qualifiers on the statement: p:P551/ps:P551 place, pq:P580 start, pq:P582 end. To include containing areas (e.g., NYC boroughs), expand via wdt:P551/wdt:P131*. Durations usually need client-side calc on QLever.
3. Ticker symbols are pq:P249 on p:P414 statements; query via the statement node (?org p:P414 ?st . ?st ps:P414 ?ex ; pq:P249 ?ticker). Use VALUES to pre-limit orgs/exchanges. Don’t expect wdt:P249 on the org. Prefer qualifiers for time-bound tickers.
4. Archives: use p:P485/ps:P485 for the holding institution. Inventory numbers are qualifiers pq:P217 on that P485 statement. Don’t expect wdt:P217 directly on the person/work. “Archive descriptions” may be separate collection items (P195).
5. When listing contained municipalities or similar, prefer wdt:P150* (has parts) from the parent to enumerate children, then join other relations (e.g., twin towns via wdt:P190). Avoid broad wdt:P131+ scans from children; they are slow and can timeout.
6. On QLever, avoid SERVICE wikibase:label (frequent 301). Use OPTIONAL rdfs:label with LANG filters or fetch QIDs then labels separately. For property mapping, (?prop wikibase:directClaim ?p). Pre-limit with subselect/VALUES to avoid timeouts.
7. Employer constraints: to find people employed by UN or international orgs, use wdt:P108 directly for UN (wd:Q1065), or traverse employer to part of (wdt:P361*) UN, or employer wdt:P31 wd:Q484652 (international organization). Combine with other occupations.
8. For sports/events/editions, prefer explicit edition items (e.g., Q47345468) with wdt:P361 linking to the parent series/tour and filter by wdt:P585/P571 for year; avoid P641/P2139 that model sports played or participants, not the edition metadata.
9. For author/creator queries, use occupation wdt:P106 (e.g., author/writer) rather than P31 typing. To list works, prefer the reverse path ^wdt:P50 ?work; P800 (notable work) is incomplete and curated, not a full bibliography.
10. Awards: use p:P166/ps:P166 and constrain award via wdt:P31/wdt:P279* to a target class (e.g., Cannes awards Q28444913). Recipients can be films or people; don’t assume film-specific properties exist. Count/group by recipient type if needed.
11. To select current/active codes or memberships on QLever, use statement nodes (p:/ps:) and MINUS { ?st pq:P582 [] }. For time series counts (e.g., daily members), generate a date series (VALUES/UNNEST), then test overlap with pq:P580/pq:P582 per date.
12. For people’s native names, use wdt:P1559 (name in native language) on the person, not rdfs:label. Return multiple if multiple native languages exist; pick a preferred language client-side if needed.
13. For multi-valued props (e.g., P1082), GROUP BY entity and aggregate (MAX/MIN/SAMPLE) to avoid duplicates; DISTINCT won’t collapse multiple statements. For category/gender counts, prefer indicator sums: SUM(IF(cond,1,0)) over COUNT on OPTIONAL vars.
14. Avoid SERVICE wikibase:label on QLever; it often 301s. Use OPTIONAL rdfs:label with LANG filters, or fetch QIDs first and labels in a follow-up. Pre-limit with subselect/VALUES to avoid timeouts when joining many labels.
15. For P551 duration comparisons, avoid unsupported date arithmetic. If needed, compute overlaps client-side. On-endpoint, you can only compare presence/counts or use simple MIN/MAX of dates (casting and arithmetic are limited in QLever).
16. When excluding specific entities from a relation (e.g., siblings), use FILTER to drop explicit QIDs or FILTER NOT EXISTS with a VALUES list. Ensure you use the exact sibling QIDs returned by the KG, not assumed ones.

General notes for all knowledge graphs:
1. When checking date interval overlaps, handle open intervals (missing start/end) and use xsd:dateTime. Use OR conditions to cover start within, end within, or spanning the whole range.
2. For P39 queries, qualifiers (e.g., P2937 term, P768 electoral district, P4100 parliamentary group) live on the p:P39 statement node. Do not expect them as wdt: properties on the person or use ps: for non-main values.
3. To get sitelink counts, use wikibase:sitelinks on the entity; it returns a single numeric value, so GROUP BY the entity and avoid COUNT over ?sitelink.
4. Use subclass expansion for types: wdt:P31/wdt:P279* target (e.g., dams, educational institutions). This captures items modeled with subclasses.
5. For locations, prefer hierarchies via wdt:P131+ to reach a containing region/state, and wdt:P17 for country. If HQ is a building, P159 ps points to a city; specific site is qualifier pq:P276 on the P159 statement.
6. When excluding or selecting by a legislative term on P39, check pq:P2937 on the relevant statement. Use FILTER NOT EXISTS over p:P39 with ps:P39 target and pq:P2937 value to exclude a term.
7. QLever endpoints may not support Wikidata’s “WITH {…} AS %name” and “INCLUDE %name” syntax. Avoid named subqueries; use nested SELECTs or VALUES instead.
8. The wikibase:label SERVICE often fails on QLever. Prefer rdfs:label with FILTER(LANG(..)="en") or get QIDs only and resolve labels client-side.
9. Avoid COUNT over OPTIONAL variables that may be unbound for all rows; prefer EXISTS/BOUND checks or aggregate over DISTINCT entities to prevent misleading zeros.
10. On QLever, heavy OPTIONAL label/property joins often time out. Pre-limit with a subselect/VALUES over IDs (ORDER BY + LIMIT), then join labels/properties. Or fetch QIDs first and labels in a second, smaller query.
11. For precise date filtering on Wikidata (birth/death), prefer p/psv time nodes and wikibase:timeValue plus timePrecision checks over wdt:P569/P570 to include values with year/month precision and avoid silent drops.
12. When filtering by exact day of birth or event, avoid STRSTARTS on wdt:P569; instead bound an interval [day, next day) with xsd:dateTime to include all precisions. On QLever, add hint:Prior hint:rangeSafe true to improve performance on time ranges.

You can use the following SPARQL prefixes implicitly in all functions:
cc: <http://creativecommons.org/ns#
data: <https://www.wikidata.org/wiki/Special:EntityData/
dct: <http://purl.org/dc/terms/
geo: <http://www.opengis.net/ont/geosparql#
geof: <http://www.opengis.net/def/function/geosparql/
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/
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/
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#
foaf: <http://xmlns.com/foaf/0.1/
dc: <http://purl.org/dc/elements/1.1/
gn: <http://www.geonames.org/ontology#
bd: <http://www.bigdata.com/rdf#
hint: <http://www.bigdata.com/queryHints#
qb: <http://purl.org/linked-data/cube#
void: <http://rdfs.org/ns/void#

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.

Additional rules:
1. Explain your thought process before and after each step and function call.
2. Do not just use or make up entity or property identifiers without verifying their existence in the knowledge graphs first.
3. Always execute your final SPARQL query before giving an answer to make sure it returns the expected results.
4. 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.
5. 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.
6. 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.
7. For questions with a "True" or "False" answer the SPARQL query should be an ASK query.
8. 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.

[User] What are the distinct lithostratigraphic units located in Arizona? Please include any parts they have (if available, the larger units they are part of (if available), and their Geolex IDs (if available).

[Assistant]
Let's break down the question:

1. We are looking for lithostratigraphic units (rock units classified by lithology) located in Arizona.
2. For each unit, we want:
   - Any parts they have (sub-units)
   - Any larger units they are part of
   - Their Geolex IDs (if available)

Step 1: Identify the entity for "lithostratigraphic unit" in Wikidata.
Step 2: Find the property for "located in" or "location" to filter for Arizona.
Step 3: Find properties for "has part" (sub-units) and "part of" (larger units).
Step 4: Find the property for "Geolex ID".

Let's proceed step by step.

First, search for "lithostratigraphic unit" in Wikidata.

[Tool]
Top 10 entity alternatives:
1. lithostratigraphic unit, also known as rock unit (wd:Q3550897)
2. former lithostratigraphic unit (wd:Q109902873)
3. sedimentary lithostratigraphic unit (wd:Q28021934)
4. 1, also known as multiplicative identity, Ⅰ, number 1, ₁, ⅰ (wd:Q199): instance of centered dodecahedral number, instance of heptagonal pyramidal number, instance of pentagonal pyramidal number, instance of centered pentachoric number, instance of centered tetrahedral number, instance of centered icosahedral number, instance of centered octahedral number, instance of centered pentagonal number, instance of hexagonal pyramidal number, instance of centered triangular number, instance of centered heptagonal number, instance of centered nonagonal number, instance of centered decagonal number, instance of centered octagonal number, instance of centered hexagonal number, instance of square triangular number, instance of multiplicative identity, instance of stella octangula number, instance of square pyramidal number, instance of centered square number, instance of centered cube number, instance of non-negative integer, instance of dodecahedral number, instance of dodecagonal number, instance of tetrahedral number, instance of icosahedral number, instance of dimensionless unit, instance of automorphic number, instance of heptagonal number, instance of pentagonal number, instance of triangular number, instance of hexagonal number, instance of decagonal number, instance of coherent SI unit, instance of pentatope number, instance of octagonal number, instance of Fibonacci number, instance of nonagonal number, instance of Mersenne number, instance of unit of amount, instance of natural number, instance of harshad number, instance of square number, instance of power of 1000, instance of seventh power, instance of power of two, instance of eighth power, instance of fourth power, instance of fifth power, instance of power of 10, instance of ninth power, instance of sixth power, instance of star number, instance of odd number, instance of repunit, natural number one, instance of cube, instance of unit, instance of {1}
5. unit of measurement, also known as unit of measure, unit, measurement unit (wd:Q47574)
6. apartment, also known as flats, unit, flat, dwelling (wd:Q188507)
7. lithostratigraphy, also known as lithostratigraphic, lithostratigraphical (wd:Q856124)
8. division, also known as section, organizational division, organizational unit, organizational section, business division (wd:Q334453)
9. unit, also known as invertible element (wd:Q118084)
10. enzyme unit, also known as unit, U (wd:Q636200): unit of catalytic activity; one micromole per minute; 16.66… nanokatals, instance of unit of catalytic activity

[Assistant]
The main entity for "lithostratigraphic unit" is wd:Q3550897.

Next, let's search for the property that links an entity to its location, so we can filter for those located in Arizona.

[Tool]
Top 10 property alternatives:
1. work location, also known as worked from, work place, working from, working at, worked at (wd:P937 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): location where persons or organisations were actively participating in employment, business or other work, subproperty of significant place, subproperty of location
2. location, also known as neighborhood, locale, neighbourhood, place, place held (wd:P276 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): location of the object, structure or event. In the case of an ad...ity use P706. Use P7153 for locations associated with the object
3. coordinate location, also known as gps co-ordinates, wgs 84, gps coordinates, gps location, latitude (wd:P625 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): geocoordinates of the subject. For Earth, please note that only WGS84 coordinating system is supported at the moment
4. occupant, also known as location of, tenant, resident, renter, occupiers (wd:P466 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): person or organization occupying property, subproperty of used by
5. applies to jurisdiction, also known as country of jurisdiction, of, jurisdiction linked, jurisdiction, belongs to jurisdiction (wd:P1001 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): the item (institution, law, public office, public register...) o...a territorial jurisdiction: a country, state, municipality, ...), subproperty of characteristic of, subproperty of significant place, subproperty of operating area
6. recorded at studio or venue, also known as recording venue, venue, studio, recording studio, recorded at event (wd:P483 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): studio or location where a musical composition/release was recorded, subproperty of recording location
7. home venue, also known as venue, stadium, home water, home ground, home field (wd:P115 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): home stadium or venue of a sports team or applicable performing arts organization, subproperty of location
8. published in, also known as tome of, tome of the book, track of, track on, track on album (wd:P1433 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): larger work that a given work was published in, like a journal, a website, a collection, a book or a music album, subproperty of part of
9. located in the present-day administrative territorial entity, also known as present-day administrative territorial entity, located in the current administrative territorial entity, located in the modern-day administrative territorial entity, located in the present-day administrative territorial entity, located in present day administrative territorial entity (wd:P3842 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): the item was located in the territory of this present-day administrative unit; however the two did not at any point coexist in time, subproperty of location, subproperty of part of
10. directions, also known as locality or place (wd:P2795 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): describe how to find the subject - directions, objects along way, comments

[Assistant]
The most general property for location is wd:P276 ("location"). There is also wd:P3842 ("located in the present-day administrative territorial entity"), which is more precise for modern locations. For Arizona, the present-day entity is likely best.

Now, let's search for the entity for "Arizona" to use as the location filter.

[Tool]
Top 10 entity alternatives:
1. Arizona, also known as Grand Canyon State, US-AZ, The Grand Canyon State, State of Arizona, AZ (wd:Q816): state of the United States of America, instance of U.S. state
2. University of Arizona, also known as UA, Univ. of Arizona, University of Az, U.A., U of A (wd:Q503419): instance of public educational institution of the United States, public university in Tucson, Arizona, United States, instance of open-access publisher, instance of land-grant university, instance of public university
3. Arizona (wd:Q2254748): municipality in Atlántida Department, Honduras, instance of municipality of Honduras
4. Arizona (wd:Q670059): 1940 film by Wesley Ruggles, instance of film
5. Arizona (wd:Q634389): 1918 silent film drama, instance of film
6. Arizona (wd:Q2861452): 1913 film by Augustus Thomas, instance of silent film, instance of film
7. Arizona, also known as Glossy snake (wd:Q14089080): instance of taxon, genus of reptiles
8. Arizona (wd:Q4791227): municipality and village in San Luis, Argentina, instance of municipality, instance of locality
9. Arizona, also known as Men Are Like That (wd:Q3196815): 1931 film by George B. Seitz, instance of film
10. Arizona (wd:Q2325768): instance of comic book album, Lucky Luke comic

[Assistant]
The correct entity for the U.S. state of Arizona is wd:Q816.

Next, let's find the properties for "has part" (for sub-units), "part of" (for larger units), and "Geolex ID".

I'll search for the "has part" property first.

[Tool]
Top 10 property alternatives:
1. has part(s), also known as has ingredient, has ingredients, had part, has member, has part (wd:P527 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): part of this subject; inverse property of "part of" (P361). See also "has parts of the class" (P2670).
2. applies to part, also known as applies to aspect, applied to, when viewed as, valid for part, section (wd:P518 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): part, aspect, or form of the item to which the claim applies
3. based on, also known as modelled after, inspired by, iteration of, modeled after, input (wd:P144 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): the work(s) or inputs used as the basis for subject item; for fictional analog use P1074, subproperty of references work, tradition or theory, subproperty of inspired by
4. proportion, also known as %, part, percent, ratio, share (wd:P1107 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): to be used as a qualifier, value must be between 0 and 1
5. combines lexemes, also known as contain (lexeme), prefix, contains (lexeme), has part (lexeme), have part (lexeme) (wd:P5238 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): subproperty of derived from lexeme, lexemes combined in this lexeme
6. part of, also known as meronym of, contained within, of, part of-property, section of (wd:P361 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): object of which the subject is a part (if this subject is alread... of "has part" (P527, see also "has parts of the class" (P2670))
7. depicted part, also known as part depicted, part shown, shown part (wd:P5961 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): use as qualifier for "depicts" (P180)
8. parent organization, also known as parent company, parent institution, parent organisation, parent unit, part of (wd:P749 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): parent organization of an organization, opposite of subsidiaries (P355), subproperty of owned by, subproperty of part of
9. partially coincident with, also known as partially include, overlaps, partially in, partial concurrency, overlaps with (wd:P1382 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): object that partially overlaps with the subject in its instances, parts, or members, subproperty of different from
10. number of parts of this work, also known as number of movements, number of parts of this work of art, number of pictures, number of segments of anthology film, number of songs (wd:P2635 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): the number of parts that a work comprises

[Assistant]
The property for "has part" is wd:P527, and the property for "part of" is wd:P361.

Now, let's search for the property for "Geolex ID".

[Tool]
Top 10 property alternatives:
1. Geolex ID, also known as GEOLEX ID, Geolex identifier (wd:P6202 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): ID for every stratigraphic unit in the United States of America (USA) given by the United States Geological Survey
2. coordinate location, also known as gps co-ordinates, wgs 84, gps coordinates, gps location, latitude (wd:P625 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): geocoordinates of the subject. For Earth, please note that only WGS84 coordinating system is supported at the moment
3. GeoNames ID, also known as GeoNames, Geonames Id (wd:P1566 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): identifier in the GeoNames geographical database
4. geoshape, also known as Commons map data, geographic data, geographic shape, .map, map data (wd:P3896 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): geographic data from Wikimedia Commons
5. GSS code (2011), also known as ONS ID, ONS GSS code (2011), GSS code (2009), GEOGCD, ONS GSS code (2009) (wd:P836 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): nine-character UK Government Statistical Service code, introduced in 2009 to replace older ONS codes
6. Géopatronyme ID, also known as Geopatronyme ID (wd:P3370 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): identifier of a family name in the Géopatronyme database
7. GeoLOD ID, also known as GeoLOD identifier (wd:P12170 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): identifier for a place in Japan
8. GeolISSTerm ID, also known as GeolISSTerm identifier, Geološki Informacioni Sistem Srb...logija i nomenklatura identifier, Geološki Informacioni Sistem Srb... terminologija i nomenklatura ID, Geološka terminologija i nomenklatura identifier, Geološka terminologija i nomenklatura ID (wd:P10748 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): identifier for a term in the GeolISSTerm terminology dictionary
9. Interlex ID, also known as Neurolex ID (wd:P696 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): identifier in the Interlex database (used to be Neurolex)
10. Geokod (wd:P1172 as pqv/prv/psn/pqn/wdt/pr/p/psv/wdtn/prn/ps/pq): identifier for historical administrative division of Sweden (1862-1951)

[Assistant]
The property for "Geolex ID" is wd:P6202.

Now, let's summarize the plan for the SPARQL query:
- Select all entities that are instances of "lithostratigraphic unit" (wd:Q3550897)
- Located in Arizona (wd:Q816), using either wd:P276 or wd:P3842
- For each, get:
  - Their parts (wd:P527)
  - The larger unit they are part of (wd:P361)
  - Their Geolex ID (wd:P6202)

To ensure we get all relevant units, I'll check which property is more commonly used for location: wd:P276 or wd:P3842, by listing triples for lithostratigraphic units with these properties.

[Tool]
Got 68 rows and 3 columns, showing the first 10 rows below:
| subject                                                              | property            | object            |
| -------------------------------------------------------------------- | ------------------- | ----------------- |
| Bernie Sanders 2020 presidential campaign in Arizona (wd:Q105653669) | location (wdt:P276) | Arizona (wd:Q816) |
| Cochise Tradition (wd:Q1105140)                                      | location (wdt:P276) | Arizona (wd:Q816) |
| Second Powell Expedition (wd:Q110928544)                             | location (wdt:P276) | Arizona (wd:Q816) |
| CopperCon (wd:Q112624890)                                            | location (wdt:P276) | Arizona (wd:Q816) |
| DarkCon (wd:Q112625354)                                              | location (wdt:P276) | Arizona (wd:Q816) |
| Arizona wildfire season (wd:Q113680707)                              | location (wdt:P276) | Arizona (wd:Q816) |
| 2024 Arizona Republican presidential primary (wd:Q116783471)         | location (wdt:P276) | Arizona (wd:Q816) |
| economy of Arizona (wd:Q11681256)                                    | location (wdt:P276) | Arizona (wd:Q816) |
| Arizona Freedom Caucus (wd:Q117832637)                               | location (wdt:P276) | Arizona (wd:Q816) |
| Project Harvest (wd:Q122785117)                                      | location (wdt:P276) | Arizona (wd:Q816) |
| ...                                                                  | ...                 | ...               |

[Tool] Got no rows and 3 columns

[Assistant]
It appears that wd:P276 ("location") is used for entities located in Arizona, while wd:P3842 is not used for Arizona in this context.

Now, let's check if lithostratigraphic units use wd:P276 to indicate their location. I'll list some triples with subject type wd:Q3550897 and property wd:P276.

[Tool]
Got 65,536 rows and 3 columns, showing the first 10 rows below:
| subject                            | property            | object                 |
| ---------------------------------- | ------------------- | ---------------------- |
| Hitchcock Hall (wd:Q100974511)     | location (wdt:P276) | United States (wd:Q30) |
| anarchism in Russia (wd:Q1033142)  | location (wdt:P276) | Russia (wd:Q159)       |
| posthumous name (wd:P1786)         | location (wdt:P276) | Japan (wd:Q17)         |
| Festivalbar (wd:Q1000984)          | location (wdt:P276) | Italy (wd:Q38)         |
| Free Spirit Tour (wd:Q1003754)     | location (wdt:P276) | Germany (wd:Q183)      |
| 2021 UCI ProSeries (wd:Q101371171) | location (wdt:P276) | Europe (wd:Q46)        |
| Storm Barbara (wd:Q100631590)      | location (wdt:P276) | France (wd:Q142)       |
| cinema of Finland (wd:Q1001500)    | location (wdt:P276) | Finland (wd:Q33)       |
| wd:Q102323460                      | location (wdt:P276) | Mexico (wd:Q96)        |
| Cyclone Nivar (wd:Q102323954)      | location (wdt:P276) | India (wd:Q668)        |
| ...                                | ...                 | ...                    |

[Tool]
Got 21 rows and 3 columns, showing the first 10 rows below:
| subject                            | property              | object                                |
| ---------------------------------- | --------------------- | ------------------------------------- |
| Muschelkalk (wd:Q1543962)          | instance of (wdt:P31) | lithostratigraphic unit (wd:Q3550897) |
| Apex Chert (wd:Q10854294)          | instance of (wdt:P31) | lithostratigraphic unit (wd:Q3550897) |
| Blue Granite (wd:Q110715941)       | instance of (wdt:P31) | lithostratigraphic unit (wd:Q3550897) |
| Composite Gneiss (wd:Q110715947)   | instance of (wdt:P31) | lithostratigraphic unit (wd:Q3550897) |
| Alpha Granite (wd:Q110716003)      | instance of (wdt:P31) | lithostratigraphic unit (wd:Q3550897) |
| Tropico Group (wd:Q123519690)      | instance of (wdt:P31) | lithostratigraphic unit (wd:Q3550897) |
| Bissell Formation (wd:Q123519770)  | instance of (wdt:P31) | lithostratigraphic unit (wd:Q3550897) |
| Gem Hill Formation (wd:Q123520088) | instance of (wdt:P31) | lithostratigraphic unit (wd:Q3550897) |
| wd:Q2206072                        | instance of (wdt:P31) | lithostratigraphic unit (wd:Q3550897) |
| Eigenbilzen Member (wd:Q2664591)   | instance of (wdt:P31) | lithostratigraphic unit (wd:Q3550897) |
| ...                                | ...                   | ...                                   |

[Tool] Got no rows and 3 columns

[Tool] Got no rows and 3 columns

[Tool] Got no rows and 3 columns

[Tool] Got no rows and 3 columns

[Tool] Got no rows and 3 columns

[Tool] Got no rows and 3 columns

[Tool] Got no rows and 3 columns

[Tool] Got no rows and 3 columns

[Tool] Got no rows and 3 columns

[Tool]
Top 10 entity alternatives:
1. stratigraphic unit, also known as geological unit, geologic unit (wd:Q3694119)
2. Algonkian (stratigraphic unit) (wd:Q2646567): the youngest unit of the Canadian Precambrian, instance of stratigraphic unit
3. Australian Stratigraphic Units Database, also known as ASUD, National Register of Stratigraphic Names (wd:Q64380918): database of stratigraphic units in Australia, instance of database
4. New Devonian stratigraphic units (wd:Q96067769): scientific article published in 1941, instance of scholarly article
5. Australian Stratigraphic Units Database ID (wd:P2367): identifier for a stratigraphic unit listed in the Australian Stratigraphic Units Database, instance of Wikidata property for authority control, instance of Wikidata property related to geology
6. Correlation of Great Basin stratigraphic units (wd:Q95710624): instance of scholarly article
7. Stratigraphic units in space and time (wd:Q113648357): scientific article published in December 1959, instance of scholarly article
8. Australian Geological Provinces ID, also known as Australian Geological Provinces Database Identifier, Australian Stratigraphic Units Database Province ID, ASUD Province ID (wd:P2742): identifier of a geologic province in the Australian Geological Provinces Database published by Geoscience Australia, instance of Wikidata property for authority control, instance of Wikidata property related to geology
9. 1, also known as multiplicative identity, Ⅰ, number 1, ₁, ⅰ (wd:Q199): instance of centered dodecahedral number, instance of heptagonal pyramidal number, instance of pentagonal pyramidal number, instance of centered pentachoric number, instance of centered tetrahedral number, instance of centered icosahedral number, instance of centered octahedral number, instance of centered pentagonal number, instance of hexagonal pyramidal number, instance of centered triangular number, instance of centered heptagonal number, instance of centered nonagonal number, instance of centered decagonal number, instance of centered octagonal number, instance of centered hexagonal number, instance of square triangular number, instance of multiplicative identity, instance of stella octangula number, instance of square pyramidal number, instance of centered square number, instance of centered cube number, instance of non-negative integer, instance of dodecahedral number, instance of dodecagonal number, instance of tetrahedral number, instance of icosahedral number, instance of dimensionless unit, instance of automorphic number, instance of heptagonal number, instance of pentagonal number, instance of triangular number, instance of hexagonal number, instance of decagonal number, instance of coherent SI unit, instance of pentatope number, instance of octagonal number, instance of Fibonacci number, instance of nonagonal number, instance of Mersenne number, instance of unit of amount, instance of natural number, instance of harshad number, instance of square number, instance of power of 1000, instance of seventh power, instance of power of two, instance of eighth power, instance of fourth power, instance of fifth power, instance of power of 10, instance of ninth power, instance of sixth power, instance of star number, instance of odd number, instance of repunit, natural number one, instance of cube, instance of unit, instance of {1}
10. unit of measurement, also known as unit of measure, unit, measurement unit (wd:Q47574)

[Tool]
Got 14 rows and 3 columns, showing the first 10 rows below:
| subject                                      | property              | object                           |
| -------------------------------------------- | --------------------- | -------------------------------- |
| wd:Q105737732                                | instance of (wdt:P31) | stratigraphic unit (wd:Q3694119) |
| Phenix City Gneiss (wd:Q105849827)           | instance of (wdt:P31) | stratigraphic unit (wd:Q3694119) |
| Baltic sandstone (wd:Q106486421)             | instance of (wdt:P31) | stratigraphic unit (wd:Q3694119) |
| Upper Baltic sandstone (wd:Q106486422)       | instance of (wdt:P31) | stratigraphic unit (wd:Q3694119) |
| wd:Q10709467                                 | instance of (wdt:P31) | stratigraphic unit (wd:Q3694119) |
| Jizera Formation (wd:Q108392192)             | instance of (wdt:P31) | stratigraphic unit (wd:Q3694119) |
| Supergroup Espinhaço (wd:Q113374581)         | instance of (wdt:P31) | stratigraphic unit (wd:Q3694119) |
| Ariano unit (wd:Q118867722)                  | instance of (wdt:P31) | stratigraphic unit (wd:Q3694119) |
| Valentine Formation (wd:Q18358011)           | instance of (wdt:P31) | stratigraphic unit (wd:Q3694119) |
| Algonkian (stratigraphic unit) (wd:Q2646567) | instance of (wdt:P31) | stratigraphic unit (wd:Q3694119) |
| ...                                          | ...                   | ...                              |

[Tool] Got no rows and 3 columns

[Tool] Got no rows and 3 columns

[Tool] Got no rows and 3 columns

[Tool]
Top 10 entity alternatives:
1. geological formation, also known as formation, geological formation, geologic formation (wd:Q736917)
2. geological formation (wd:L23956-S1)
3. Geological formation near Socola (wd:Q28916514): geological and paleonthological natural monument of Moldova, instance of geological formation
4. DUPLICATION OF GEOLOGIC FORMATION NAMES (wd:Q94553893): scientific article published in April 1899, instance of scholarly article
5. DUPLICATION OF GEOLOGIC FORMATION NAMES (wd:Q80997956): scientific article published on 01 April 1899, instance of scholarly article
6. Geologic formation operations framework control (wd:Q122196510): instance of United States patent, US patent 11429670
7. Geological Formations of Iowa (wd:Q61037620): instance of scholarly article
8. The Geological Formation of Britain (wd:Q87347008): instance of radio series episode, episode of In Our Time
9. THE DUPLICATION OF GEOLOGIC FORMATION NAMES (wd:Q81105567): instance of scholarly article, scientific article
10. Synchronism of geological formations (wd:Q94559417): instance of scholarly article

[Tool]
Got 9,982 rows and 3 columns, showing the first 10 rows below:
| subject                                | property              | object                            |
| -------------------------------------- | --------------------- | --------------------------------- |
| Tordillo Formation (wd:Q100235565)     | instance of (wdt:P31) | geological formation (wd:Q736917) |
| Ignacio Quartzite (wd:Q100366128)      | instance of (wdt:P31) | geological formation (wd:Q736917) |
| Elbert Formation (wd:Q100366213)       | instance of (wdt:P31) | geological formation (wd:Q736917) |
| Picuris Formation (wd:Q100768092)      | instance of (wdt:P31) | geological formation (wd:Q736917) |
| Bungle Bungle Range (wd:Q1009481)      | instance of (wdt:P31) | geological formation (wd:Q736917) |
| Colored Dolomite (wd:Q1009776)         | instance of (wdt:P31) | geological formation (wd:Q736917) |
| Masonic Park Tuff (wd:Q101072089)      | instance of (wdt:P31) | geological formation (wd:Q736917) |
| Ra Jadero Tuff (wd:Q101072106)         | instance of (wdt:P31) | geological formation (wd:Q736917) |
| Treasure Mountain Tuff (wd:Q101072210) | instance of (wdt:P31) | geological formation (wd:Q736917) |
| Alai Beds (wd:Q101313779)              | instance of (wdt:P31) | geological formation (wd:Q736917) |
| ...                                    | ...                   | ...                               |

[Tool]
Got 68 rows and 3 columns, showing the first 10 rows below:
| subject                                                              | property            | object            |
| -------------------------------------------------------------------- | ------------------- | ----------------- |
| Bernie Sanders 2020 presidential campaign in Arizona (wd:Q105653669) | location (wdt:P276) | Arizona (wd:Q816) |
| Cochise Tradition (wd:Q1105140)                                      | location (wdt:P276) | Arizona (wd:Q816) |
| Second Powell Expedition (wd:Q110928544)                             | location (wdt:P276) | Arizona (wd:Q816) |
| CopperCon (wd:Q112624890)                                            | location (wdt:P276) | Arizona (wd:Q816) |
| DarkCon (wd:Q112625354)                                              | location (wdt:P276) | Arizona (wd:Q816) |
| Arizona wildfire season (wd:Q113680707)                              | location (wdt:P276) | Arizona (wd:Q816) |
| 2024 Arizona Republican presidential primary (wd:Q116783471)         | location (wdt:P276) | Arizona (wd:Q816) |
| economy of Arizona (wd:Q11681256)                                    | location (wdt:P276) | Arizona (wd:Q816) |
| Arizona Freedom Caucus (wd:Q117832637)                               | location (wdt:P276) | Arizona (wd:Q816) |
| Project Harvest (wd:Q122785117)                                      | location (wdt:P276) | Arizona (wd:Q816) |
| ...                                                                  | ...                 | ...               |

[Tool]
Got 1 row and 3 columns:
| subject                         | property              | object                     |
| ------------------------------- | --------------------- | -------------------------- |
| Cochise Tradition (wd:Q1105140) | instance of (wdt:P31) | Paleo-Indians (wd:Q888099) |

[Tool]
Got 1 row and 3 columns:
| subject                                                              | property              | object                          |
| -------------------------------------------------------------------- | --------------------- | ------------------------------- |
| Bernie Sanders 2020 presidential campaign in Arizona (wd:Q105653669) | instance of (wdt:P31) | political campaign (wd:Q847301) |

[Tool]
Got 1 row and 3 columns:
| subject                           | property              | object                            |
| --------------------------------- | --------------------- | --------------------------------- |
| Ignacio Quartzite (wd:Q100366128) | instance of (wdt:P31) | geological formation (wd:Q736917) |

[Tool] Got no rows and 3 columns

[Tool]
Top 10 entity alternatives:
1. Supai Group (wd:Q7641892): Section of red bed deposits at the Colorado Plateau, instance of group
2. The Supai Group of Grand Canyon (wd:Q61047468): scientific article published in 1982, instance of scholarly article
3. The Supai Group; subdivision and nomenclature (wd:Q61461300): scientific article published in 1975, instance of scholarly article
4. group, also known as Mathematical group, Group (math), mathematical group, algebraic group, Group (algebra) (wd:Q83478)
5. group, also known as periodic table group, family, column of elements (wd:Q83306)
6. functional group, also known as group, radical (wd:Q170409)
7. squad, also known as group, squad (military), Sqd., military squad (wd:Q207063)
8. musical group, also known as band, music group, music band, musical project, musical band (wd:Q215380)
9. substituent group, also known as side chain, substituted, substituent atom, substituent, side group (wd:Q898422)
10. Supai, also known as Supai, AZ (wd:Q3476581): instance of census-designated place in the United States, census-designated place in Coconino County, Arizona

[Tool]
Got 1 row and 3 columns:
| subject                   | property            | object                    |
| ------------------------- | ------------------- | ------------------------- |
| Supai Group (wd:Q7641892) | location (wdt:P276) | Grand Canyon (wd:Q118841) |

[Tool]
Got 1 row and 3 columns:
| subject                   | property                                                    | object            |
| ------------------------- | ----------------------------------------------------------- | ----------------- |
| Grand Canyon (wd:Q118841) | located in the administrative territorial entity (wdt:P131) | Arizona (wd:Q816) |

[Assistant]
The Supai Group (wd:Q7641892) is located in the Grand Canyon (wd:Q118841), which is in Arizona (wd:Q816). This shows that some lithostratigraphic/geological units are linked to Arizona via intermediate locations.

Therefore, to capture all relevant units, the query should:
- Find all geological formations (wd:Q736917) or lithostratigraphic units (wd:Q3550897) or stratigraphic units (wd:Q3694119)
- That are located in Arizona (wd:Q816), either directly (wdt:P276) or via a location (wdt:P276) that is in Arizona (wdt:P131+)
- For each, get their parts (wdt:P527), larger units (wdt:P361), and Geolex ID (wdt:P6202)

Now, I will write a SPARQL query that:
- Finds all items that are an instance of wd:Q736917, wd:Q3550897, or wd:Q3694119
- That are located in Arizona, either directly or via a containing location
- Returns their parts, larger units, and Geolex ID (if available)
- Optionally includes labels for human readability

Let's construct and execute this query.

[Tool]
Got 20 rows and 7 columns, showing the first 5 and last 5 rows below:
| unit                              | unitLabel               | geolex           | part                                | partLabel                 | larger                     | largerLabel      |
| --------------------------------- | ----------------------- | ---------------- | ----------------------------------- | ------------------------- | -------------------------- | ---------------- |
| Bright Angel Shale (wd:Q14563356) | Bright Angel Shale (en) | BrightAngel_4814 | Boucher Tongue (wd:Q64300755)       | Boucher Tongue (en)       | Tonto Group (wd:Q7821714)  | Tonto Group (en) |
| Bright Angel Shale (wd:Q14563356) | Bright Angel Shale (en) | BrightAngel_4814 | Elves Chasm Tongue (wd:Q64301508)   | Elves Chasm Tongue (en)   | Tonto Group (wd:Q7821714)  | Tonto Group (en) |
| Bright Angel Shale (wd:Q14563356) | Bright Angel Shale (en) | BrightAngel_4814 | Flour Sack Member (wd:Q64302358)    | Flour Sack Member (en)    | Tonto Group (wd:Q7821714)  | Tonto Group (en) |
| Bright Angel Shale (wd:Q14563356) | Bright Angel Shale (en) | BrightAngel_4814 | Garnet Canyon Tongue (wd:Q64302848) | Garnet Canyon Tongue (en) | Tonto Group (wd:Q7821714)  | Tonto Group (en) |
| Bright Angel Shale (wd:Q14563356) | Bright Angel Shale (en) | BrightAngel_4814 | Lava Falls Tongue (wd:Q64304385)    | Lava Falls Tongue (en)    | Tonto Group (wd:Q7821714)  | Tonto Group (en) |
| ...                               | ...                     | ...              | ...                                 | ...                       | ...                        | ...              |
| Galeros Formation (wd:Q64317035)  | Galeros Formation (en)  | Galeros_5378     | Carbon Canyon Member (wd:Q64317197) | Carbon Canyon Member (en) | Chuar Group (wd:Q16958225) | Chuar Group (en) |
| Galeros Formation (wd:Q64317035)  | Galeros Formation (en)  | Galeros_5378     | Duppa Member (wd:Q64317460)         | Duppa Member (en)         | Chuar Group (wd:Q16958225) | Chuar Group (en) |
| Galeros Formation (wd:Q64317035)  | Galeros Formation (en)  | Galeros_5378     | Jupiter Member (wd:Q64317797)       | Jupiter Member (en)       | Chuar Group (wd:Q16958225) | Chuar Group (en) |
| Galeros Formation (wd:Q64317035)  | Galeros Formation (en)  | Galeros_5378     | Tanner Member (wd:Q64318046)        | Tanner Member (en)        | Chuar Group (wd:Q16958225) | Chuar Group (en) |
| Toroweap Formation (wd:Q7826713)  | Toroweap Formation (en) | Toroweap_10913   | Brady Canyon Member (wd:Q62474335)  | Brady Canyon Member (en)  |                            |                  |

[Tool] Stopped generation process