Wikidata Entity Scraper - Knowledge Graph Data
Pricing
from $4.00 / 1,000 results
Wikidata Entity Scraper - Knowledge Graph Data
Search or fetch Wikidata entities with labels, descriptions, aliases, claims, statement counts, sitelinks, and Wikipedia URLs in structured form.
Pricing
from $4.00 / 1,000 results
Rating
0.0
(0)
Developer
Thirdwatch
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Wikidata Entity Scraper
Search or fetch Wikidata knowledge-graph entities with labels, aliases, claims, statements, sitelinks, and Wikipedia URLs.
What you get
Turn names, concepts, or exact Q-IDs into structured knowledge-graph rows. Search in a chosen language, fetch exact entities without injecting an unrelated default search, and enrich every match through Wikidata's entity API. Output includes human-readable metadata, simplified claim values, counts for statements and sitelinks, and direct Wikidata and language-matched Wikipedia links.
Output fields
| Field | Description |
|---|---|
id, label, description | Entity identity and readable metadata |
aliases | Alternative names in the requested language |
matched_text, matched_type | Search-match context when applicable |
claims | Property IDs mapped to simplified statement values |
statements_count, sitelinks_count | Entity richness indicators |
wikipedia_url, entity_url | Language Wikipedia and Wikidata links |
source, license | Wikidata attribution and CC0 license |
Example output
Input parameters
| Parameter | Required | Description |
|---|---|---|
queries | No | Entity names or concepts; empty permits exact-only lookup |
entityIds | No | Exact IDs such as Q42 or Q7259 |
language | No | Language code for search and labels; defaults to en |
maxResultsPerQuery | No | Maximum search matches per query; defaults to 10 |
Use cases
- Data teams can enrich names with durable knowledge-graph identifiers.
- Publishers can connect topics to Wikipedia and multilingual references.
- Researchers can inspect statement and sitelink coverage across entities.
- Developers can seed entity-resolution and taxonomy workflows.
Limitations
Wikidata is community-maintained, so labels, descriptions, claims, and sitelinks can change and may contain errors or gaps. Claim values are simplified for portability: complex qualifiers, ranks, references, calendars, precision, and units are not expanded into a full RDF model. Search relevance belongs to Wikidata. The Actor retrieves items, not MediaWiki pages or arbitrary SPARQL result sets.
Compared to alternatives
This Actor combines wbsearchentities and wbgetentities in one bounded Apify workflow. Unlike plain search output, it adds claims and richness counts. Unlike a SPARQL query builder, it requires no query-language knowledge and works naturally with saved Tasks, schedules, webhooks, and datasets.
FAQ
Can I fetch exact Q-IDs without a search?
Yes. Leave queries empty and provide entityIds. The Actor will not inject a default query.
Can I reuse the output commercially?
Wikidata structured data is published under CC0. Review Wikimedia's current reuse guidance for your application and preserve useful source links.
Explore Wikidata Entity Scraper on thirdwatch.dev. Related Actors: OpenAlex Research Scraper, Crossref DOI Scraper, and Google Search Scraper.
Last verified: 2026-07
