Posts
Four Query Timeline examples you can adapt
Rewritten on 28 October 2026 for the current Histropedia Query Timeline tool. The original publication date is retained above.
A useful example should show how to adapt it, not just open a finished view. These four recipes use the current Histropedia Query Timeline tool and expose the query, mappings and limitations.
| Start with | What you learn | First change to try |
|---|---|---|
| Descendants | Relationship paths, optional death dates and lifespan precision | Show children only before changing the root person |
| Places near a landmark | Geographic radius, date roles and numeric colour | Change the centre and keep a small radius |
| Paintings by an artist | Images, categorical colour and repeated result rows | Restrict the date range, then change the creator |
| Oscar winners | Dates attached to award statements and repeated events | Change the award item while keeping qualifier dates |
Open the examples
Open the descendants example · Download the SPARQL query
Open the nearby places example · Download the SPARQL query
Open the paintings example · Download the SPARQL query
Open the award winners example · Download the SPARQL query
The links include field mappings, not just query text. Results are live, capped and dependent on the statements currently in Wikidata. They are starting points for exploration, not complete catalogues. The descendants and paintings examples reached their limits during our check; their walkthroughs explain how to narrow them.
A repeatable adaptation workflow
- Open an example and inspect a few source records, including their dates and precision.
- Open Configure Timeline and make one change to the query. Keep the Main graph endpoint for these examples.
- Check the selected variables against the mapping fields. A renamed variable must also be renamed in its mapping, colour and filter settings.
- Generate the timeline and look for missing events, duplicate cards and overly precise dates.
- Test the shared link in a fresh tab. Export a snapshot if a stable result matters, retaining the query and retrieval date with it.
If a query is slow, first reduce its scope: a smaller radius, a bounded relationship depth or a narrower date question. LIMIT caps the returned rows but does not necessarily make the preceding computation cheap. If an optional field becomes a required pattern, records missing that field disappear; that is a common cause of a suddenly smaller timeline.
The complete workflow guide explains event identity, date precision, grouping, density and the choice between a live query and an exported snapshot. These recipes replace the old gallery’s shortened links and beta-era instructions.