Structured Knowledge Platform
Structured Knowledge Platform Group
[edit]Mission
[edit]Wikimedia stewards a large body of knowledge that is structured, verifiable, and available in many languages. This is something that automatically generated content cannot easily replicate. The Structured Knowledge Platform group maintains part of this body of knowledge in the form of structured facts, reusable logic, and articles written in a language-independent form. People create this knowledge once, and it can be reused across languages, with every output tracing back to a human source. Our group's mission is to keep this knowledge reliable and easy to build on, so encyclopedic knowledge can more easily grow and stay up to date, and more readers can find what they're looking for in their own language.
Team Members
[edit]| Product | Design | Community | Program Management |
|---|---|---|---|
|
Gregory Onyeahialam (Senior UX Designer) |
|
Aida Ramirez (Technical Program Manager) |
| Engineering | ||
|---|---|---|
|
|
|
FY27 Objectives
[edit]We are focused on the following goals from July 1, 2026 to June 30, 2027 ("FY27"):
Abstract Wikipedia on language wikis
[edit]Demonstrate Abstract Wikipedia's viability as a scalable, human-centered way to create multilingual encyclopedic content. The Internet is increasingly shaped by automatically produced text that is often opaque and unverifiable. At the same time, manually created knowledge alone cannot adequately fill multilingual content gaps. Can Wikipedia’s human-led model of knowledge creation scale across languages without sacrificing trust, transparency, or community control? By making one contribution reusable across many languages, Abstract Wikipedia seeks to answer that question. It does this by bringing together three Wikimedia projects. Wikifunctions turns facts from Wikidata into language-independent sentences, and Abstract Wikipedia renders them as articles in each supported natural language.
Wikidata Platform backend migration
[edit]Migrate the Wikidata Query Service backend from Blazegraph to Qlever: The Wikidata Platform backend replacement will offer capacity improvements for Wikidata, Wikidata Query Service (WDQS), and all systems integrated with either tool. We are beginning our migration with a small group of pilot users to baseline migration efforts and user impact of the new backend. Our goal is to be fully migrated to the new backend by the end of year.
Scope
[edit]The Structured Knowledge Platform group enables builders, contributors, and re-users who depend on structured knowledge. Here are some ways to collaborate with us:
- Querying structured data - Access to Wikidata structured data through the query service. We work on endpoint reliability and performance, rate limits, federation, and bulk access for tools and bots. In FY27, we are also working on SPARQL compatibility and query rewrites for the Wikidata backend migration.
- Turning structured data into readable content - Generating multilingual sentences and articles from Wikidata facts using Abstract Wikipedia and Wikifunctions, and integrating generated content into language wikis.
- Reusable logic across wikis - Writing, running, and calling Wikifunctions from other Wikimedia projects, and function evaluation as a service for teams that need shared computation.
- Contributing to structured knowledge projects - Editing surfaces, onboarding, feedback, and community processes for Abstract Wikipedia and Wikifunctions contributors.
- Trust and provenance of generated content - Increasing community trust of content generated from structured knowledge.
- Building on the platform - If your team or tool depends on structured facts, functions, or multilingual prose, and you are looking for platform capabilities to help you reach your goals, let's talk!
These products and services are not within our group's scope:
- Wikimedia Commons
- Wikidata.org, Wikibase, and Wikibase Cloud
- Translation tools
Building on the Platform
[edit]Here are some possibilities for how teams could build on the platform in the future:
- Editing teams could surface suggested edits when a fact like a country's population is in Wikidata but missing from an article, or flag conflicts between Wikidata and an infobox.
- Reading teams could add maps and timelines generated from Wikidata that update as the data changes, or use Wikifunctions to show units and dates in the format a reader expects.
- Smaller language Wikipedias could get a generated starting point for new articles instead of a blank page.
- Reach out if you have ideas you'd like to discuss with us!