Wikidata Extractor avatar

Wikidata Extractor

Pricing

from $0.17 / 1,000 results

Go to Apify Store
Wikidata Extractor

Wikidata Extractor

Extract structured knowledge from Wikidata — the free, open knowledge base. Search by term or fetch exact entities (Q-IDs) and get clean labels, descriptions, aliases, and a flattened claims map with human-readable property names. No API key required.

Pricing

from $0.17 / 1,000 results

Rating

0.0

(0)

Developer

Cynix Dev

Cynix Dev

Maintained by Community

Actor stats

1

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

Extract structured knowledge from Wikidata — the free, open knowledge base. Search by term or fetch exact entities (Q-IDs) and get clean labels, descriptions, aliases and a flattened claims map with human-readable property names. No API key required.

What it does

Wikidata is the structured backbone behind Wikipedia — millions of entities with typed statements. This Actor searches it by term or fetches exact entities by Q-ID, and returns the useful parts flattened: label, description, aliases, sitelinks and a claims map where property IDs are resolved to readable names (so P31 becomes "instance of").

It's the knowledge-enrichment primitive: resolve "Berlin" to structured facts, or pull a batch of entities to build a knowledge graph.

Features

  • Search or fetch — free-text term, or exact Q-IDs.
  • Flattened claims — property IDs resolved to human-readable names.
  • Labels, descriptions, aliases — in the language you choose.
  • Sitelinks — links to Wikipedia and sister projects per wiki.
  • Keyless public API — no API key, no proxy.

What people use it for

  • Knowledge-graph building — structured facts about entities at scale.
  • Entity enrichment — attach Wikidata claims to your own records.
  • Disambiguation — resolve a term to the right entity and Q-ID.
  • NLP and QA — grounding answers in a structured source.
  • Dataset linking — bridge internal IDs to Wikidata entities.

Reading the claims map

Each claim is stored as a property ID + value. The Actor resolves the property ID to its name so the data is legible:

  • P31 → "instance of"
  • P569 → "date of birth"
  • P1082 → "population"

Values themselves may be entity IDs (Q...) or literals; for nested entities you'd resolve the Q-ID in a second call. This keeps one record per entity while preserving the structure.

Language

language controls labels, descriptions and aliases. Wikidata is multilingual; the same entity has labels in many languages, so pick the one your users read.

Input

Provide searchTerm for a search, or entityIds (Q-IDs) for direct fetch — Q-IDs win when both are set. language selects label language.

FieldTypeDefaultWhat it does
searchTermstringFree-text search to resolve Wikidata entities, e.g. 'Berlin', 'Elon Musk', 'COVID-19'. Used when no entity IDs are supplied.
entityIdsarray[]Exact Wikidata Q-IDs to fetch directly, e.g. ["Q64", "Q5"]. Wins over searchTerm if set.
languagestringenLanguage code for labels/descriptions, e.g. en, de, fr.
maxResultsinteger5Max entities when searching by term. Range 1–50.
proxyConfigurationobjectsee belowWikidata is a free, public API and does not require a proxy. Leave disabled.

Input example

{
"searchTerm": "Berlin",
"maxResults": 2,
"language": "en",
"proxyConfiguration": {
"useApifyProxy": false
}
}

Output

One record per entity: id, label, description, aliases, a flattened claims map, and sitelinks.

Every dataset record contains: entityId, label, description, aliases, claims, sitelinks, fetchedAt.

Output example

A real record from a run of this Actor:

{
"entityId": "Q64",
"label": "Berlin",
"description": "federated state, capital and largest city of Germany",
"aliases": "Berlin, Germany; DE-BE",
"claims": "{\"highest point\":[\"Q19259618\"],\"topic's main Wikimedia portal\":[\"Q3248436\"],\"instance of\":[\"Q1901835\",\"Q200250\",\"Q1307779\",\"Q15974307\",\"Q42744322\",\"Q133442\",\"Q114401982\",\"Q51929311\",\"Q1221156\",\"Q257391\",\"Q707813\",\"Q67123 …",
"sitelinks": "[\"itwikivoyage\",\"ukwikivoyage\",\"svwikivoyage\",\"ruwikivoyage\",\"rowikivoyage\",\"ptwikivoyage\",\"frwikivoyage\",\"hewikivoyage\",\"viwikivoyage\",\"zhwikivoyage\",\"dewikisource\",\"eowikiquote\",\"nnwikiquote\",\"enwikiquote\",\"itwikiquote …",
"fetchedAt": "2026-08-21T13:10:47.284Z"
}

Export the dataset as JSON, CSV, Excel, XML or JSONL from the Console, or pull it programmatically through the Apify API and any of the official clients.

How to use it

  1. Click Try for free (or Start if you already have an Apify account).
  2. Fill in the input fields described above — the defaults already produce a working run.
  3. Press Start and watch the log; results stream into the dataset as they are found.
  4. When the run finishes, open the Output/Storage tab and export as JSON, CSV or Excel.

Runs can be scheduled (hourly, daily, weekly) and wired into Slack, Google Sheets, Zapier, Make, webhooks or your own backend through Apify integrations. Everything the Console does is also available over the Apify API.

Proxy configuration

This Actor accepts a standard Apify proxy configuration object. Residential proxy is the default because the target site rate-limits datacenter IP ranges; you can select a specific exit country or supply your own proxy URLs.

{
"proxyConfiguration": {
"useApifyProxy": true,
"apifyProxyGroups": [
"RESIDENTIAL"
]
}
}

Pricing

This Actor is billed on Apify's pay-per-event model: a small charge when a run starts, plus a charge for each result written to the dataset. You only pay for records you actually receive — a run that finds nothing costs only the start event. Current rates are always shown on the Pricing tab of this page, and the run log prints your usage as it goes.

Free-plan credits from Apify cover a large amount of light usage, so you can evaluate the Actor before committing to anything.

FAQ

Do I need an API key?

No. Wikidata's API is public and keyless.

Why are some claim values just Q-IDs?

Wikidata stores relationships as entity references. The Actor resolves property names for you, but resolving the value entity is a separate fetch — chain another call if you need the value's label.

How current is the data?

Wikidata is edited continuously by volunteers; popular entities are very fresh, obscure ones less so.

Is this affiliated with the Wikimedia Foundation?

No. It uses Wikidata's public API and is not affiliated with, endorsed by, or operated by the Wikimedia Foundation.

Other Actors by cynix_dev

ActorWhat it does
arXiv Papers ExtractorSearch arXiv and extract papers as clean typed records: title, abstract, authors, categories, DOI, and direct PDF links.
CoinGecko Markets — Crypto Data APILive cryptocurrency market data from CoinGecko as clean typed JSON: price, market cap, volume, 24h change, ATH/ATL, …
FX Rates & HistoryLatest and historical foreign exchange rates (ECB reference data) as clean, typed dataset records.
USGS Earthquakes — GeoJSON ExtractorPull live and historical earthquakes from the USGS FDSN event service as clean typed JSON: magnitude, place, time, lat/lon/depth, …
Launch Library 2 — Rocket Launch TrackerUpcoming, previous, and specific rocket launches from The Space Devs' Launch Library 2 API.
Open Food Facts ExtractorSearch and extract food-product data from Open Food Facts as clean typed JSON: name, brand, ingredients, allergens, nutrition …

This Actor collects only publicly available information. You are responsible for how you use the data, including compliance with the target site's Terms of Service, robots directives, copyright, and data protection law such as GDPR and CCPA. Do not use it to gather personal data without a lawful basis.

Support and feedback

Found a bug, hit a site change, or need an extra field? Open a ticket on the Issues tab of this Actor — issues are read and fixed. Feature requests and custom-scraper enquiries are welcome through the same channel.