lookup-person-wikidata

Resolves ambiguous person references by querying Wikidata for candidate names, birth years, and Q-ids.

Updated May 9, 2026
One-click install
npx skills add https://github.com/anneschuth/polder --skill lookup-person-wikidata
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lookup-person-wikidata
Source: https://github.com/anneschuth/polder/tree/main/.claude/skills/lookup-person-wikidata
Command: npx skills add https://github.com/anneschuth/polder --skill lookup-person-wikidata

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When creating new person records for Dutch government entities, ambiguous name references often lead to unstable UUID-based slugs instead of human-readable ones that include birth years. This skill solves that by querying Wikidata to find matching person candidates with their Q-ids and birth years, so you can use stable, meaningful slugs for new records.

Core Features & Use Cases

  • Disambiguated Person Lookup: Accepts full names or structured name objects (family, given, initials) plus optional context like organization or role to narrow down matches.
  • Scored Candidate Matching: Ranks Wikidata results by name similarity and context fit, returning a recommended match only when confidence exceeds 0.85 to avoid incorrect assignments.
  • Cached, Safe Output: Caches lookup results to avoid repeated network calls, and only writes output to staging directories to prevent accidental direct edits to production person data. Use Case: For example, when adding a new director for the BZK directie Digitale Samenleving, use this skill to first check if they have a Wikidata entry, so their person slug includes their birth year instead of a random UUID.

Quick Start

Use the lookup-person-wikidata skill to find Wikidata candidates for the person named Suzie Kewal who works at BZK directie Digitale Samenleving.

Frequently Asked Questions about lookup-person-wikidata

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get birth years for person disambiguation in Dutch public sector datasets?

You provide full names or structured name objects along with optional context like organization or role. The tool queries Wikidata to rank candidates by name similarity and context fit, returning a recommended match only when confidence exceeds 0.85.

Can I use organization and role context to improve person matching in government datasets?

Yes, providing optional context like organization and role helps disambiguate candidates with low name similarity. The tool applies this context to rank Wikidata results and improve match accuracy for government entity records.

What is the best way to generate stable slugs instead of UUIDs for new person records?

Lookup Wikidata persons to retrieve stable Q-ids and birth years, enabling you to generate human-readable slugs that include birth years instead of unstable UUID-based identifiers for new person records.

Does Wikidata person lookup cache results to avoid redundant network calls?

Yes, the lookup caches results to eliminate redundant network calls. It also enforces output to staging directories to prevent accidental direct edits to production person data during the matching process.

Are there limitations for Wikidata person matching when confidence is below 0.85?

When confidence falls below 0.85, no recommended match is returned to prevent incorrect assignments. You receive a scored candidate list instead, requiring manual review before creating a new person record.