Posts

Build an Oscar winners timeline from Wikidata award statements

Rewritten on 28 October 2026 for the current Histropedia Query Timeline tool. The original publication date is retained above.

An award timeline should show when the award was recorded, not the winner’s birth date. In Wikidata that date can live on the award statement as a qualifier. This example builds a Query Timeline view of Best Actress winners using the statement’s point-in-time value.

Open this example in Query Timeline · Download the SPARQL query

# Best Actress winners by the point-in-time qualifier on the award statement.
SELECT DISTINCT ?item ?itemLabel ?itemDescription ?start ?startPrecision
  ?citizenshipLabel
WHERE {
  ?item p:P166 ?awardStatement .
  ?awardStatement ps:P166 wd:Q103618 ; pqv:P585 ?dateValue .
  ?item wdt:P31 wd:Q5 .
  FILTER NOT EXISTS { ?awardStatement wikibase:rank wikibase:DeprecatedRank . }
  ?dateValue wikibase:timeValue ?start ;
             wikibase:timePrecision ?startPrecision .
  OPTIONAL { ?item wdt:P27 ?citizenship . }
  SERVICE wikibase:label { bd:serviceParam wikibase:language "en" . }
}
ORDER BY ?start ?item
LIMIT 300

Why this query starts from a statement

P166 means award received. The path ?item p:P166 ?awardStatement gives access to a particular award statement; ps:P166 wd:Q103618 selects the Best Actress award. pqv:P585 reaches the point-in-time qualifier’s value node, where the query reads both date and precision. Requiring wdt:P31 wd:Q5 restricts recipients to humans: some film records also carry acting-award statements.

That qualifier is required here. Award statements without a usable point-in-time value are omitted, rather than assigned the person’s birth date, the film’s release date or a guessed ceremony date. The result is a view of dated award statements, not an authoritative or exhaustive list of winners. Inspect a statement and its references to understand whether its date denotes a ceremony day or a year; these are not necessarily the film’s eligibility year.

Keep repeat winners on their separate dates

The supplied link maps itemLabel to title, itemDescription to description, start to start date and startPrecision to start precision. It leaves the end date empty, links item as the Wikidata/source record, and enables duplicate merging grouped by item.

Grouping combines repeated rows with matching start dates; the same recipient winning in different years remains separate. In this single-category query, that is the intended behaviour. If you combine categories and someone wins several awards on the same date, grouping only by person can collapse distinct awards: return and group by an event key such as the award statement instead.

The optional citizenship property can produce several rows for a recipient. citizenshipLabel is available for colours and filters, and itemLabel for a recipient filter. Citizenship in the person’s record is not necessarily citizenship at the time of the award; do not interpret the colour as a historical nationality claim. Missing citizenship data does not exclude the award.

Adapt the same query to five categories

In Configure Timeline, change only the award identifier on the ps:P166 line, update the title and generate again:

Category Wikidata item
Best Actress Q103618
Best Actor Q103916
Best Supporting Actress Q106301
Best Supporting Actor Q106291
Best Director Q103360

The query excludes deprecated award statements, orders results by date and caps the response at 300 rows before grouping. Several citizenships can use several rows for one win. Check the result size when adapting it and investigate missing years at the source rather than assuming the award did not exist.

Share the method as well as the result

Use Share for a configured link or embed, then reopen it to confirm the mappings. Use Export for a dated snapshot, retaining the query and retrieval date alongside it. The general Query Timeline guide explains precision and grouping in more detail.

This replaces the five legacy shortened links with an inspectable query that you can adapt and audit.

comments powered by Disqus