A portfolio that can be read as a knowledge graph
This page parses the JSON-LD out of its own document head and draws the result. The artifact and the demonstration are the same file. Click a node to inspect its properties, drag to reposition, follow an edge to traverse.
Entity graph · jakelabate.com
Counts reflect a full parse of the production sitemap. Every node carries a resolvable @id, which is what lets separate pages reference one shared entity instead of each re-declaring its own.
Why this is the component and not a paragraph
A portfolio can claim entity fluency. This page is the claim and the evidence in the same DOM. View source and the graph you are looking at is right there in a script tag.
Self referential
The renderer reads application/ld+json from its own document. Change the schema, the graph changes. There is no separate fixture to drift out of sync.
@id as the join key
Nodes connect on @id references rather than nesting. That is the difference between a graph and a pile of duplicated blobs.
sameAs as reconciliation
External identity edges are what let a retrieval system decide that this Jake Labate and that LinkedIn profile are one entity.