Germany’s AI innovation path

What public evidence proves—and where the link ends

The evidence path connects German EU funding participation to reported research outputs through exact CORDIS identifiers. Patents and procurement remain visibly separate until a shared official identifier proves the link.

  • Exact project and PIC identifiers
  • Uncertain links excluded
  • Deterministic · no generator
Bounded, exactly linked starting cohortProjection dated 14 Jul 2026, 17:19Observed since 13 Jul 2026
German net EU allocation€13.85M

German participation only within the exactly linked CORDIS projects

Proven project paths8

CORDIS project code and participant PIC agree in both sources

Project-output relations582

OpenAIRE relations, not claims of authorship or impact

Reported citations12,960

OpenAIRE metadata, not a quality or impact score

Evidence-path explorer

Follow every proven step

Choose a project and inspect its identifiers, funding amount, research outputs and the deliberately open transitions to patents and public procurement.

8 paths
H2020 · 101007799

Innovations to accelerate vaccine development and manufacture

01 Sept 2021 to 28 Feb 2027

CORDIS project ↗
  1. 01proven

    EU allocation

    German project participation

    €1.70M

    Reported net EU contribution to German participants in this CORDIS project.

  2. 02proven

    Participating organisation

    EUROPEAN VACCINE INITIATIVE EV

    PIC 886899810

    Role reported by CORDIS: coordinator.

  3. 03proven

    Reported research

    Inno4Vac

    76 outputs

    74 with open access; 724 reported citations.

  4. 04in progress

    Patent families

    German-associated AI patents

    Collector in progress

    EPO OPS provides patent families but no stable organisation identifier for an automatic project link.

  5. 05not linked

    Public procurement

    Tender to contract

    No exact bridge

    OCDS and TED party identifiers cannot currently be equated safely with CORDIS PICs.

Evidence register

Every edge carries its proof

Chronology is not causality. The register therefore shows which relation is exactly proven and which remains open because no shared identifier exists.

StatusRelationLink basisSource
provenFunding record belongs to the selected projectCORDIS project code 101007799CORDIS ↗
provenGerman participant belongs to the allocation rowCORDIS PIC 886899810CORDIS ↗
provenOpenAIRE products are reported against the projectOpenAIRE project ID corda__h2020::3ff8c2eae210596e6529f3875ee87b4e + CORDIS 101007799OpenAIRE ↗
openPatent family belongs to project or organisationEPO supplies no stable applicant identifier for a cross-source joinEPO OPS ↗
openProcurement belongs to project or organisationNo shared official identifier between PIC and procurement partyOCDS / TED ↗
Gaps are data

What we explicitly refuse to guess

The path becomes more valuable because missing bridges stay visible. A name, similar address or shared region is not enough for an organisation or impact claim.

01 · Patents

Applicant names are not global IDs

DOCDB patent families can be collected automatically. We only publish a link to CORDIS, ROR or LEI when a source-backed shared identifier exists.

02 · Procurement

Source-local parties remain separate

TED and OCDS identifiers connect lifecycles within their source. They are not merged with funded organisations through name similarity.

03 · Impact

Chronology does not prove cause

Funding before an output, patent or contract is a time pattern. The index does not label it commercialisation or funding impact.

Method & identity rules

A conservative data spine

The public path is built only from relations that both participating sources support with compatible identifiers.

  1. 1
    Intersect exact project codes

    An allocation row enters the path only when its CORDIS project code exactly matches the transfer project.

  2. 2
    Confirm participants through PIC

    The German organisation must carry the same CORDIS PIC in funding and transfer data. Names are display values, never join keys.

  3. 3
    Check output relations twice

    The OpenAIRE project ID and CORDIS grant identifier must both occur in the product relation.

  4. 4
    Preserve disconnected lanes

    Patent and procurement data keep their own source identities. Candidates, fuzzy matches and private review data never reach the website.

Collection, classification and linking do not invoke a generative AI model.

Sources & coverage

The first public revision is deliberately bounded. Every source entry discloses its own scope; missing data is never reinterpreted as zero.

European Commission CORDISbounded cohort
8 records

Bounded transfer probe with exact grant identifiers and German participant PICs.

checked 14 Jul 2026, 17:19Open official source ↗
OpenAIRE Graphfully checked
582 records

Reported research products and project relations; the public view is bounded while project aggregates come from the fully checked run.

checked 14 Jul 2026, 17:19Open official source ↗
European Commission CORDISfully checked
1,869 records

Official Horizon Europe bulk data underlying the funding and participant records.

checked 13 Jul 2026, 11:22Open official source ↗
European Commission CORDISfully checked
2,267 records

Official Horizon 2020 bulk data underlying the funding and participant records.

checked 13 Jul 2026, 11:22Open official source ↗
European Patent Office · OPSaccess to configure

The collector is implemented but requires one-time EPO OPS access setup before its first automated run. Patent data remains unknown—not zero—until then.

Open official source ↗
Datenservice Öffentlicher Einkauf · TEDnot linked

Procurement lifecycles are already collected daily. A source-backed shared identifier with CORDIS participants is not currently available.

Open official source ↗

Frequently asked questions

Does the path show what funding caused?
No. It shows reported allocations, project participation and research-product relations in chronological order. This proves neither causality nor economic impact.
Why not connect organisations by name?
Legal forms, spelling, corporate groups and subsidiaries make names ambiguous. A false merge could assign money, patents or contracts to the wrong organisation. We therefore require compatible source-backed identifiers.
Why are patents and procurement not shown as zero?
Not linked does not mean none exist. Without a safe identity bridge, the project-level count is unknown, so we deliberately avoid showing zero.
What will the patent collector capture?
The plan covers DOCDB patent families with publication, priority, CPC and observation data from EPO OPS. German applicant, inventor, priority and publication associations remain separate signals.
Does an OpenAIRE relation prove German authorship?
No. CORDIS proves German project participation; OpenAIRE proves a product relation to the project. Without a separate exact organisation identifier, we make no authorship claim.
Does the collector use generative AI?
No. The complete path uses versioned rules, exact identifiers, schema validation and traceable source evidence.
Traceable data products

Want to connect data sources without inventing evidence?

We build robust collectors, archives and analysis pipelines with clear identity rules and verifiable provenance.

Discuss a projectView all tools