https://eureka.patsnap.com/resources/blog/rd-blog/knowledge-graph-co-reference-resolution-across-multiple-documents-patent-landscape/ · Patsnap · data cut-off 2026-10-16 · downloaded from the live page
Patent Landscape

Knowledge Graph Co-Reference Resolution Across Documents: Patent Data

Covers 8 patent families on coreference resolution across documents in knowledge graphs, where one filer holds 2 of 8 families.

12
Published Records
8
Simple Patent Families
42%
In Force at Cut-off
US
Leading Jurisdiction

12 published records collapse into 8 simple (DOCDB) families; the difference is the same invention filed in more than one country. In force = 5 of 12 records still granted and maintained at the data cut-off; the rest are pending, withdrawn, refused or lapsed.

  • 8 simple patent families and 12 published records sit inside this search. No date limit was set, so this is every matching record the string returns.
  • Salesforce Inc is named on 2 of the 8 families, the largest single row. The other 6 listed filers hold 2 or fewer families each.
  • 5 of the 12 published records were granted and still in force at retrieval. The remainder are pending, withdrawn, refused or lapsed, not broken out here.
Check your own idea
Published byPatsnap Research··5 min readSourced from Patsnap Eureka
Overview

What this dataset covers

This page reports every record matching a search for knowledge graph coreference resolution across multiple documents, with no start or end date applied to the query. The search returns 12 published records, which de-duplicate to 8 simple patent families once filings for the same invention across different offices are merged. Records and families are different counts for the same underlying set and are never interchangeable on this page.

8 families is a small pool. Treat this page as a starting point for a further search rather than a map of a field: absence of a name or a branch here is as likely to reflect the search string as it is to reflect what has actually been filed.

Records vs. families in scope
  1. SALESFORCE INC2
  2. NEC LAB EURO GMBH1
  3. Information Engineering University of the PLA Cyberspace Force1
  4. PERSISTENT SYSTEMS1
  5. THE UNITED STATES OF AMERICA AS REPRESENTED BY THE SECRETARY OF THE NAVY1
  6. NEC CORP1
  7. MICROSOFT TECHNOLOGY LICENSING LLC1

Ordered by volume only, not by importance or claim strength. Counted in simple (DOCDB) patent families, so one invention filed in several countries counts once. Names come from Patsnap's standardised assignee field as recorded on each document; subsidiaries and group companies are not merged. The icon before each name is read from the name itself (words such as University, Institute or Ltd); the data carries no organisation-type field, so treat it as a reading aid rather than a classification. Filings held by named individuals rather than organisations are removed where they can be identified; that identification is not exhaustive, so an individually held filing can still appear below. Either way those filings stay inside the totals above. This table shows the top 7 of the 7 filers returned for this search; the data endpoint returns at most 100 entities, so even that 7 is not the complete set of filers. A single family can name more than one filer, so these counts overlap and do not add up to the total.

Source: Patsnap Eureka. Assignee ranking and totals. Derived from one Patsnap search for Knowledge Graph Co-Reference Resolution Across Multiple Documents Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-16. Counts cover published records only and move as new filings publish.Run this in Eureka MCP

Let an AI agent run this analysis on your own technology

Pick a task. Every answer cites the patents behind it.

10,000 free credits to start
The Numbers

Filings, filers and classification

Three views of the same 8 families and 12 records: who filed, when the records were published, and which IPC subclasses the families sit under.

Filing trend by earliest filing year (published records)

Records run from 2018 through 2026, peaking so far at 4 in 2025. Years from 2022 on are still filling in as later filings publish, so the recent end of this line should not be read as a drop-off.

Filing trend by earliest filing year (published records)012342201820192020202120222023202442025120262022 onwards are shaded as still filling in: a filing is only visible once it publishes, up to 30 months after filing.

Counted in published records by earliest filing year, not de-duplicated into families. A filing is counted in the year it was filed, but it only becomes visible after it publishes: roughly 18 months for most routes, and up to 30 months where a PCT application enters national phase. 2022 onwards are therefore still filling in and are shaded; no growth figure on this page uses them. Because this series counts documents rather than inventions, a rise can mean more inventions or the same inventions filed in more countries; this dataset cannot separate the two.

IPC subclass composition (share of 8 families)

G06F (electric digital data processing) appears on 7 of the 7 families, 87.5%. G06N (computing based on AI models) appears on 3 of the 8, 37.5%. A family can carry both classes, so these shares add to more than 100%.

IPC subclass composition (share of 8 families)G06F · Electric digital data processi…787.5%G06N · Computing based on AI models337.5%G06Q · Business, commerce & admin dat…112.5%

Shares are the percentage of the 8 patent families in scope. One patent family can carry several IPC classes, so the shares add up to more than 100%.

Source: Patsnap Eureka. Filing trend and technology composition. Derived from one Patsnap search for Knowledge Graph Co-Reference Resolution Across Multiple Documents Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-16. Counts cover published records only and move as new filings publish.

Go deeper on Knowledge Graph Co-Reference Resolution Across Multiple Documents Patent Landscape with Eureka

This page is one run against one query. Ask Eureka your own question about knowledge graph co-reference resolution across multiple documents patent landscape and every answer comes back with the patent numbers behind it.

Try Eureka
Representative Filing

A record from the result set

Representative Record
US20190361961A12019-11-28

Fact validation in document editors

MICROSOFT TECHNOLOGY LICENSING LLC

The abstract describes a validation service for statements made while a user creates or edits a document. Statements are submitted to the service, which resolves coreferences in the statement, then resolves entities, then resolves predicates, and uses the resulting entity-predicate pairs to traverse a knowledge graph.This is the first record returned under the database's default order, not the most cited, newest or broadest filing in the set. It is shown to illustrate what one filing in scope looks like, not as representative of the other 7 families.

US20190361961A1, patent drawing 1US20190361961A1, patent drawing 2
View full record

Selected as the first record the search returns under the database default order, then shown in full. It is not ranked by citations, claim breadth or commercial importance, and it is not a judgement about which filing in this space matters most.

Source: Patsnap Eureka. The first record the search returned, shown in full. Derived from one Patsnap search for Knowledge Graph Co-Reference Resolution Across Multiple Documents Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-16. Counts cover published records only and move as new filings publish.Run this in Eureka MCP
Run it yourself

Put your own technology through the same analysis


  
Where to run it
Fastest

Eureka on the web

When you want the answer in the next five minutes.

The agent works the prompt against patents and technical literature, citing every source.

Run your analysis now →
For builders

MCP server & REST API

When it has to run inside your own pipeline.

Patent search, landscape analysis and assignee resolution as MCP tools. Drop them into any agent framework, or call REST directly.

Browse MCP servers →
Signals

Reading the dataset without overreading it

Each figure below is reported as counted in the evidence; none of them is summed across rows or extended into a market-wide claim.

Largest single filer
2 of 8 families
Salesforce Inc

One row at 25.0%

Salesforce Inc is named on 2 of the 8 simple patent families in scope, 25.0%. This is the single largest row in the listed filers; it is not added to any other row here, because families can name more than one filer and the rows overlap.

Filer table, families basis
Long tail
7 of 7 filers
At 2 families or fewer

Every listed filer holds 2 or fewer families

All 7 of the 7 listed filers hold 2 or fewer of the 8 simple patent families each. That spread, rather than a combined percentage, is the honest way to describe how filings are distributed across the listed organisations.

Filer table, families basis
Legal status
5 of 12 records
Granted and in force

42% in force at retrieval

5 of the 12 published records were granted and still in force at the 2026-10-16 retrieval date. The remaining records are pending, withdrawn, refused or lapsed in some mix that is not broken out on this page, and legal status changes continuously after retrieval.

Legal status, records basis
Receiving offices
4 offices
US 6 · PCT 4 · CN 1 · IN 1

Filing destinations, not filer origin

The 12 published records were filed across 4 receiving offices: United States (6), WIPO/PCT (4), China (1) and India (1). This describes where applications were filed, not where any filer is based; no nationality data is included in this dataset.

Receiving office, records basis
Eureka AI Agent
Looking for what nobody has claimed yet?

Eureka can read the same corpus for gaps instead of for coverage: under-claimed branches adjacent to knowledge graph co-reference resolution across multiple documents patent landscape, with the prior art for and against each one.

Find the white space →
Source: Patsnap Eureka. Derived observations on the same dataset. Derived from one Patsnap search for Knowledge Graph Co-Reference Resolution Across Multiple Documents Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-16. Counts cover published records only and move as new filings publish.Run this in Eureka MCP
Next Steps

Where to take this from here

This page is a starting point built from one search string. Refining the scope or reading specific claim sets is the next step for any of the angles below.

Read the granted claims directly

A family count or an abstract cannot establish what a granted claim covers. Anyone assessing freedom to operate against a specific record in this set needs to pull its claim set and prosecution history.

Open Patsnap Eureka

Widen or narrow the search string

With 8 families in scope, small changes to the search terms can move records in or out of the pool. Testing adjacent phrasing is a reasonable next step before drawing conclusions from this set alone.

Open Patsnap Eureka

Track new publications as they land

Records from 2022 onward are still filling in as later filings publish. Revisiting this search periodically will pick up filings that have not yet published.

Open Patsnap Eureka
Source: Patsnap Eureka. Suggested next steps. No new data: every figure named here is one of those above. Derived from one Patsnap search for Knowledge Graph Co-Reference Resolution Across Multiple Documents Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-16. Counts cover published records only and move as new filings publish.Run this in Eureka MCP
FAQ

Questions practitioners ask about this set

Answers are grounded in the same dataset. Derived from one Patsnap search for Knowledge Graph Co-Reference Resolution Across Multiple Documents Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-16. Counts cover published records only and move as new filings publish.Run this in Eureka MCP

Research Knowledge Graph Co-Reference Resolution Across Multiple Documents Patent Landscape in depth with Eureka

Go past this page: query the whole knowledge graph co-reference resolution across multiple documents patent landscape corpus yourself, in your own scope.
Every answer comes back with patent numbers you can open.

Try Eureka
How this page was built, and what the numbers do and do not mean

Search. Every figure on this page comes from one Patsnap search, run once and not edited afterwards. This is the exact search string:

TAC:(("knowledge graph*") AND ("coreference resolution" OR "co-reference resolution") AND (document* OR "multiple documents"))

Reading the field codes: TAC searches the title, abstract and claims of each record, not the full description. The search string sets no date limit, so the scope is every matching record in the database regardless of when it was filed. It is not restricted to recent years. How this string was built matters for how far the counts can be pushed. It was generated in batch from a topic list rather than hand-crafted for this page, and the result set is not manually screened. A keyword search over title, abstract and claims both over-captures (unrelated filings that happen to use the same words) and under-captures (the same invention written in different words). This page cannot measure either effect, so read every figure here as what this particular string returned, not as what exists in the field. One subclass (G06F) carries 87.5% of the patent families, so this search returned a classification-tight set.

What is being counted. Two different units appear on this page and they are not interchangeable. The filer list and the technology split are counted in simple (DOCDB) patent families: one invention counts once however many countries it was filed in. The total, the jurisdiction split and the filing-year chart are counted in published records: the same invention counts once per publication. For this search that is 12 records and 8 families. Record counts reward filing in many jurisdictions; family counts do not. Shares are only ever taken against a denominator in the same unit, and each one names it.

Who the filers are. Names come from Patsnap's standardised assignee field, as recorded on the documents themselves. They are not rolled up to corporate group: a parent and its subsidiaries appear as separate entries, and a portfolio acquired from another company stays under the name on the document unless the assignment is reflected there. This list is meant to carry organisations, not people. Filings held by a named individual are identified by matching the assignee against the inventors on the same search, and, for names written in Chinese, Japanese or Korean characters, by the name carrying no organisational suffix; those are removed from the list. Neither test is exhaustive: the inventor list it matches against is itself capped, and a personal name written in Latin script with no organisational wording in it cannot be told apart from a short company name by rule. So an individually held filing can still appear in the list. Those filings stay inside every total and share on this page either way, so the listed entries can add up to less than the total. A record shown in full further down still names its assignee exactly as the patent office records it, including where that is a person: that name is how the record is identified and checked. What is left out of the ranking is people as ranked entries, not people as cited sources. The table shows the top 7 of the 7 filers returned, ordered by count alone; the data endpoint returns at most 100 entities, so even that 7 is not every filer. One patent family can name several filers and each is counted separately, so these rows are not slices of a divided whole: adding them together over-counts, and this page deliberately publishes no combined "top five" share for that reason. See every filer, individuals included

Dates. The year chart counts by earliest filing year, not publication year. A filing only becomes visible once it publishes: roughly 18 months for most routes, and up to 30 months where a PCT application enters national phase. Measured across these pages, the year four back from today still holds only about 89% of its eventual count. 2022 onwards are therefore shaded on the chart as still filling in. The data behind this page was retrieved on 2026-10-16.

Legal status. "In force" counts documents whose legal status at retrieval was granted and maintained (5 of 12). Everything else is pending, withdrawn, refused, lapsed or not determinable, and those states are not broken out here because the underlying codes do not separate them cleanly. Legal status changes continuously and is reported per document, not per family. Get the status breakdown in Eureka

Classification. The technology split uses IPC subclasses (four characters, for example H01M). A single record usually carries several, so the shares add up to more than 100% and a record can appear in more than one bar. Subclass is a coarse grouping; it describes the field a record was classified into, not what the claims cover. Break the classes down to subgroup level

Who wrote the words. The tables, charts, counts, shares and patent numbers on this page are produced directly from the search result by a program; none of them are written or estimated by a language model. The surrounding prose, headings, FAQ answers and the answers in the question panel are drafted by a language model that is given those same figures and is not permitted to introduce others. Prose can still mis-describe a correct figure, so where the two disagree, the tables and charts are the record.

Disclaimer. This page is generated from Patsnap Eureka data drawn from a limited snapshot of global patent and scientific-literature records, and is provided for general information and reference only.

Patent data carries limitations that apply to every figure above. Recent filings are under-counted, because an application is not public until roughly 18 months after filing and database loading adds further delay. The search string defines and constrains everything shown: records that use different terminology, or that sit outside the fields searched, are absent and cannot be counted. Applicant names, classification codes, legal-status codes and citation records are taken as recorded and may contain errors, duplicates, omissions or stale entries. Ordering by volume is not a measure of quality, scope, enforceability or commercial value, and a larger portfolio is not a stronger one. As a result, the analysis may be incomplete or inaccurate and may not reflect the full technology landscape.

Nothing on this page constitutes an exhaustive prior-art, novelty, freedom-to-operate, validity or infringement search, nor does it constitute legal, financial, investment, or professional advice, and it should not be relied upon as such. No attorney-client relationship is created by it. Any patent, commercial, or strategic decision should be verified independently against the primary records and reviewed with qualified patent, legal, and domain professionals. Patsnap makes no warranties, express or implied, as to the accuracy, completeness, or fitness for any particular purpose of the information presented.

The question panel. The answers behind the suggested questions on this page were written when the page was generated, not in response to your click. The progress steps that play before an answer appears are an animation of how that analysis was done; nothing is being searched or computed at that moment. Typing your own question instead opens Patsnap Eureka, which does run it live.

Machine translation. Assignee and organisation names originally recorded in Chinese, Japanese or Korean have been rendered into English by an AI translation step so that the tables stay readable. These renderings are best-effort and may not match a company's registered English name; the original name is what the underlying patent record carries, and it is what any Eureka query launched from this page uses.

Help us improve

Something wrong, out of date, or missing on this page? Tell us and it goes straight to the team that maintains it.