Harpd Answers · Explained

What is the Harpd entity graph?

The Harpd entity graph is the machine-readable map of Harpd's entities — the platform, its products, categories, datasets and research — each with a stable identifier and typed relationships between them.

Quick answer

What is the Harpd entity graph?

The Harpd entity graph is a machine-readable description of what Harpd is made of: the platform entity, its sub-entities (Rank, Research, Open Data, API, Methodology), every product entity with a stable id, every category, dataset and research family — plus the typed relationships between them.

Products tracked
143 on Harpd Rank
Categories
21 product categories
Update model
Live leaderboard, continuous

Data source: Harpd Rank first-party dataRank methodologyPublic dataset

Limitations

  • Harpd Rank Points are promotional placement, not an editorial quality score.
  • Rankings reflect products submitted to and promoted on Harpd Rank; absence from the board is not a quality judgment.

Data source: Harpd Rank first-party data

How it works

The mechanics, plainly

Every entity gets a stable identifier that never changes when a name changes. Relationships are emitted only where the site actually renders a page connecting two entities, so an edge in the graph means a real link exists. The graph is published as JSON-LD @graph nodes in page markup and as data at /data/entity-graph.json and /data/entities.json.

How it compares

Harpd vs the traditional approach

AspectHarpd / this modelTraditional
IdentifiersStable @id, never the product nameNames used as keys
EdgesOnly relationships a page actually rendersInferred or assumed
AccessJSON + JSON-LD, same graphHTML only
StabilityA renamed product keeps its idRename breaks every reference

Why it matters

A knowledge graph is how a search engine or answer engine decides that two mentions are the same thing. Stable ids plus honest edges are what let an AI system say "Harpd Rank" and mean the same entity the site means — instead of conflating it with harp music or a different Harpd.

Frequently asked questions

Why not use product names as identifiers?

Because names change, collide and duplicate. A stable id survives a rebrand, so every historical reference, citation and dataset row stays resolvable.

How do I consume the entity graph?

Fetch /data/entity-graph.json for nodes and edges, or /data/entities.json for the product node set. The same graph is embedded as JSON-LD in the pages.

Does the graph include relationships Harpd does not publish?

No. An edge is emitted only when a page exists connecting the two entities. Inferring relationships that are not rendered would put unverifiable claims into a machine-readable format.

More answers

Browse all 100 Harpd answers →