ip=216.73.217.62
Semantic Knowledge Graphs

Wikidata Query Service

Public SPARQL endpoint for querying Wikidata.

slug
wikidata-query-service
priority
84
reviewed
Apr 24, 2026
Early candidatePhase 1Medium riskAPIapproved
01overview

How this source is shaped

Useful as a semantic enrichment layer. It can help connect entities, identifiers and public context, but should not be treated as an authoritative primary source for sensitive claims.

Source type
Api
Access model
Free
Pricing model
Free Public SPARQL Endpoint With Usage Limits
API available
Yes
Requires account
No
Risk level
Medium
Sensitivity
Normal
Integration phase
Phase 1
Integration priority
84
02scoring

Review dimensions

Each dimension is graded on a 0–10 scale. The overall score is a weighted aggregate.

overall score
7.61/10

Weighted aggregate across the eight review dimensions.

Authorityreputation and provenance of the source
8.00/10
Data qualityaccuracy, coverage, completeness
7.00/10
Usabilityhow quickly an analyst can extract value
6.80/10
APIshape, stability and cost of programmatic access
7.80/10
Documentationhow well the source is explained and referenced
8.00/10
Freshnesshow up-to-date the data stream is
7.20/10
Ethical fitalignment with our ethical OSINT posture
8.20/10
Commercial valueproduct leverage and monetisable surface
7.60/10
03application

Where this source fits

What analysts use it for, and — just as important — where it does not belong.

Primary use cases
  • entity_resolution
  • context_enrichment
  • public_figure_context
  • organization_context
Suitable for
  • researchers
  • developers
  • journalists
  • analysts
Not suitable for
  • primary_fact_authority_without_verification
  • high_volume_unbounded_queries
data types
knowledge_graphentitiesrelationshipsidentifierssemantic_data
04opinion

Editorial take

Our qualitative read on the source — tone, framing and trust posture.

Excellent for context, weak as final proof. Perfect as a knowledge graph helper.

05product

Integration stance

Build, buy or defer. What shape the product integration would take, and why.

Use for entity enrichment, cross-references and public context cards. Mark as secondary context, not primary verification.

06governance

Ethics and compliance

What to handle carefully, and what must not ship without sign-off.

Ethical notes

Avoid relying on community-edited data for sensitive or reputational conclusions.

Compliance notes

Respect query service limits and cache results.

07technical

Metadata

Catalog-side technical footer. Values as recorded in the source row.

source owner
Wikimedia/Wikidata community
report module
semantic_enrichment
integration candidate
true