Entity reference
This is the complete type catalogue for entities in the Packt Knowledge Graph — the shapes behind the friendly walkthrough on Enrichment & the Knowledge Graph. If you only want to understand why enrichment exists, how the overlay keeps content stable, and how links get made, start there. This page assumes you have, and lists every entity type: what it represents, the fields it carries, and worked JSON.
Two states appear throughout this page:
- Live types are shipped today and match the entity table on the overview page — you can rely on them existing in a resource's overlay right now.
- Planned types are the direction the graph is heading, drawn from active design work. Their shapes may still move before they ship. Treat a planned section as a preview, not a contract, and see Requesting a new type if your work needs one sooner than it lands.
Nothing here is a breaking change to what already exists. New types
simply appear over time — a consumer that does not recognise one falls
back to name and the mention's text, exactly as described in
Reading and consuming entities.
Nodes and attributes
Every entity in the graph is either a node or an attribute of one, and that split is the organising idea behind every table below.
- A node has its own
kg_id, its own identity, and its own lifecycle. It can be mentioned and linked to directly, and it accumulates metadata over time — a repository's star count, a person's biography. Every type in this catalogue is a node unless a section says otherwise. - An attribute never appears on its own in the overlay's top-level
entitiesarray. It only ever lives nested inside a node'smetadata— a licence string, a version number, a follower count. Attributes have nokg_idand cannot be mentioned or resolved independently of the node that carries them.
The test for which one something is: would anyone search for or link to this thing by itself? A package's licence is only ever interesting in relation to the package — it is an attribute. The package itself, and the repository it ships from, are each independently worth resolving, searching, and refreshing — they are nodes.
How metadata gets filled in
Each entity type has its own enrichment connector: a small service
that takes one detected entity, looks it up at a public source, and
returns that type's metadata. The connectors use free, openly
licensed sources — Wikipedia and Wikidata, OpenAlex, Open Library,
Crossref and DataCite, Homebrew, endoflife.date, GitHub, and the
article's own page — and each type section below says which.
Three things hold for every type:
- Every field says where it came from. Alongside the values, the
metadata carries
sources: which URL confirmed which field, and when. A later refresh can update one field without touching the rest. - Missing beats wrong. A connector leaves a field out rather than guess, and reports not found when it can't be sure it has the right thing — a lone surname, two people with the same name, a made-up example company.
kg_idcomes later. Connectors describe the thing; matching it to a graph node, and filling thekg_idon cross-references such as a language'smaintainer, happens when results are merged into the graph.
All types at a glance
Identified by is the entity's natural key, the value two mentions must share to be the same thing. Found in content by is how the detection pass (in testing) spots it. A type detection doesn't find yet can still be tagged by hand.
| Type | Identified by | Found in content by | Metadata filled by |
|---|---|---|---|
person |
name, e.g. rob-pike |
language model (full names) | connector, in testing |
organization |
name, e.g. mozilla |
language model | connector, in testing |
community |
platform and name, e.g. reddit:r/golang |
Reddit and Discord links | connector in progress |
language |
name, e.g. go |
language model | connector, in testing |
repository |
owner/name, e.g. go-chi/chi |
GitHub links | reference connector, built |
framework |
name | not yet | connector in progress |
package |
registry and name, e.g. pypi:requests |
npm, PyPI, Go module and crates.io links | connector in progress |
api |
name | not yet | connector in progress |
cloud_service |
name, e.g. aws-lambda |
list of known names | connector, in testing |
platform |
name, e.g. vercel |
list of known names | connector, in testing |
cli_tool |
name, e.g. kubectl |
list of known names | connector, in testing |
database |
name, e.g. postgresql |
list of known names | connector, in testing |
protocol |
name, e.g. oauth-2-0 |
language model | connector in progress |
rfc |
number, e.g. rfc-9110 |
"RFC 9110" in text | connector, in review (PR #429) |
conference |
name and year | not yet | connector in progress |
citation |
DOI, e.g. 10.1145/3292500.3330701 |
DOIs, written or linked | connector, in testing |
article |
name | not yet | connector, in testing |
book |
ISBN, e.g. isbn:9780134190440 |
an ISBN with its "ISBN" label | connector, in testing |
legal |
name, e.g. gdpr-article-17 |
not yet | connector, in testing |
Building or changing a connector is covered in the repo docs:
docs/services/content-lake-entity-enrichment/.
Type index
| Category | Types |
|---|---|
| Universal | person · organization · community |
| Software & infrastructure | language · repository · framework · package · api · cloud_service · platform · cli_tool · database · protocol · rfc |
| Content & publishing | article · citation · conference · book · legal · licence |
| Under review | Algorithm, design pattern, security concept |
| Excluded |
Person
Status: Live.
A notable person relevant to content — an author, a maintainer, a
speaker, a reviewer. As the overview page explains, having a person
entity is never an editorial judgement; people are discovered as the
Content Lake grows.
Fields
Filled from: Wikipedia and Wikidata for well-known people, then OpenAlex for authors and researchers without a Wikipedia page.
| Field | Type | Required | Description | Status |
|---|---|---|---|---|
about |
string|null | No | Short biography. | Live |
profiles |
array|null | No | Social/professional profiles — see Social profile. | Live |
associatedLanguages |
array|null | No | kg_id cross-references to language nodes the person is known for. |
Live |
works |
array|null | No | [{ "name", "role", "kg_id" }] — works they wrote, most cited first. |
In testing |
JSON
{
"_type": "person",
"_id": "ent-person-peter",
"kg_id": "kg_person_peter_kieltyka",
"name": "Peter Kieltyka",
"confidence": 0.88,
"salience": 0.30,
"mentions": [{ "blockKey": "b2", "startChar": 70, "endChar": 84, "text": "Peter Kieltyka" }],
"metadata": {
"about": "Creator of the Chi router for Go",
"profiles": [{ "name": "github", "url": "https://github.com/pkieltyka" }],
"associatedLanguages": ["kg_lang_go"]
}
}
Social profile (attribute)
A profile link nested in person.metadata.profiles. Kept deliberately
narrow: professional and social platform links only, never a personal
email address — see Excluded: email.
| Field | Type | Required | Description |
|---|---|---|---|
name |
string | Yes | Platform identifier: "wikipedia", "github", "x", "linkedin", "orcid", "openalex", or "website". |
url |
string | Yes | Profile URL. |
Organisation
Status: Planned — its enrichment connector is built and in
testing, so these fields are what the graph will hold once it ships.
Type identifier: organization (US spelling,
matching the enrichment contract).
A company, foundation, or standards body — the entity a repository, a conference, or a person's employment relates to (the Cloud Native Computing Foundation, Mozilla, the IETF).
Fields
Filled from: Wikipedia and Wikidata, plus the public repository count from GitHub. A page counts only when Wikidata records organisation facts (headquarters, founders, industry and so on), so concept pages and made-up examples are not found.
| Field | Type | Required | Description |
|---|---|---|---|
about |
string|null | No | Short description. |
website |
string|null | No | Official website. |
founded |
integer|null | No | Year founded. |
employees |
integer|null | No | Head count, where published. |
headquarters |
string|null | No | Headquarters city. |
githubOrg |
object|null | No | { "handle", "publicRepos" } — its GitHub account. |
JSON
{
"_type": "organization",
"_id": "ent-org-mozilla",
"kg_id": "kg_org_mozilla",
"name": "Mozilla",
"confidence": 0.92,
"salience": 0.40,
"mentions": [{ "blockKey": "b3", "startChar": 12, "endChar": 19, "text": "Mozilla" }],
"metadata": {
"about": "Free and open-source software community, developer of Firefox and Thunderbird",
"website": "https://www.mozilla.org",
"founded": 1998,
"headquarters": "San Francisco",
"githubOrg": { "handle": "mozilla", "publicRepos": 2576 }
}
}
Community
Status: Planned.
A place people gather around a technology or topic — a subreddit, a Discord server, a Slack workspace, a mailing list. Already shown as the worked "new type a consumer has never seen" example on the overview page.
Fields
| Field | Type | Required | Description |
|---|---|---|---|
platform |
string | Yes | "reddit", "discord", "slack", "mailing_list", or another free-form value. |
url |
string|null | No | Community URL, where one exists. |
members |
integer|null | No | Member count, refreshed periodically. |
JSON
{
"_type": "community",
"_id": "ent-comm-golang",
"kg_id": "kg_comm_r_golang",
"name": "r/golang",
"confidence": 0.91,
"salience": 0.35,
"mentions": [{ "blockKey": "b6", "startChar": 22, "endChar": 30, "text": "r/golang" }],
"metadata": { "platform": "reddit", "url": "https://www.reddit.com/r/golang", "members": 245000 }
}
Language
Status: Live. The connector now in testing adds the fields marked In testing.
A programming language.
Fields
Filled from: Wikipedia and Wikidata, plus the source repository's stars from GitHub.
| Field | Type | Required | Description | Status |
|---|---|---|---|---|
about |
string|null | No | Short description. | Live |
paradigm |
array|null | No | e.g. ["concurrent computing", "imperative programming"]. |
Live |
firstAppeared |
integer|null | No | Year the language first appeared. | Live |
website |
string|null | No | Official website. | Live |
version |
string|null | No | Latest stable version. | In testing |
latestStableRelease |
string|null | No | Same as version; kept for the enrichment contract. |
In testing |
maintainer |
object|null | No | { "name", "kg_id" } — the organisation or person behind it. |
In testing |
repository |
object|null | No | { "name", "stars", "kg_id" } — its canonical source Repository. |
In testing |
JSON
{
"_type": "language",
"_id": "ent-lang-go",
"kg_id": "kg_lang_go",
"name": "Go",
"confidence": 0.96,
"salience": 0.85,
"mentions": [
{ "blockKey": "b1", "startChar": 19, "endChar": 21, "text": "Go" },
{ "blockKey": "b2", "startChar": 0, "endChar": 2, "text": "Go" }
],
"metadata": {
"about": "An open-source programming language supported by Google",
"paradigm": ["concurrent computing", "imperative programming"],
"firstAppeared": 2009,
"website": "https://go.dev",
"version": "1.27.2",
"latestStableRelease": "1.27.2",
"maintainer": { "name": "Google", "kg_id": "kg_org_google" },
"repository": { "name": "golang/go", "stars": 139373, "kg_id": "kg_repo_go" }
}
}
Repository
Status: Planned. Replaces the earlier github type: the same
fields, plus host for hosts a URL alone can't identify, so GitLab,
Bitbucket and self-hosted repositories are covered as well as GitHub.
No overlays were written under the old name, so nothing needs
migrating.
A source-code repository — the live type's description, "description, licence, stars/contributors/commits, language breakdown," carries forward unchanged; only the type name and host handling change.
Filled from: the GitHub API. The repository connector is the reference every other connector copies.
Fields
| Field | Type | Required | Description |
|---|---|---|---|
href |
string | Yes | Repository URL. |
about |
string|null | No | Short description. |
host |
string|null | Conditional | "github", "gitlab", "bitbucket", or "self_hosted". Required only when the host cannot be inferred from href (e.g. a self-hosted GitLab instance). |
license |
string|null | No | SPDX licence identifier, e.g. "MIT". |
stats |
object|null | No | { "stars", "contributors", "commits", "openIssues" } — refreshed periodically. |
languages |
array|null | No | [{ "name", "proportion", "kg_id" }] language breakdown, each entry cross-referencing a Language node. |
latestRelease |
string|null | No | Tag of the latest release, where the project publishes releases. |
JSON
{
"_type": "repository",
"_id": "ent-repo-chi",
"kg_id": "kg_repo_chi",
"name": "chi",
"confidence": 0.94,
"salience": 0.70,
"mentions": [
{ "blockKey": "b1", "startChar": 26, "endChar": 29, "text": "Chi" },
{ "blockKey": "b2", "startChar": 56, "endChar": 66, "text": "Chi router" }
],
"metadata": {
"href": "https://github.com/go-chi/chi",
"about": "Lightweight, idiomatic and composable router for building Go HTTP services",
"host": "github",
"license": "MIT",
"stats": { "stars": 18900, "contributors": 120, "commits": 1450 },
"languages": [{ "name": "Go", "proportion": 0.98, "kg_id": "kg_lang_go" }]
}
}
Framework and library
Status: Planned — a specialisation of today's live generic
technology type (see the overview page's entity
table), giving frameworks
and libraries their own fields rather than sharing one catch-all shape
with every other kind of tool.
A software framework or library, e.g. React, Laravel, Django. Carries an embedded Repository cross-reference so pulling in "Laravel" also surfaces the organisation, language, and repository behind it without three separate lookups — the pattern this page's intro on nesting describes.
Fields
| Field | Type | Required | Description |
|---|---|---|---|
about |
string|null | No | Short description. |
category |
string|null | No | "framework", "library", or another free-form value. |
language |
string|null | No | kg_id of the primary Language. |
repository |
string|null | No | kg_id of the canonical Repository. |
website |
string|null | No | Official website. |
JSON
{
"_type": "framework",
"_id": "ent-fw-laravel",
"kg_id": "kg_fw_laravel",
"name": "Laravel",
"confidence": 0.93,
"salience": 0.60,
"mentions": [{ "blockKey": "b4", "startChar": 4, "endChar": 11, "text": "Laravel" }],
"metadata": {
"about": "A PHP web application framework with expressive, elegant syntax",
"category": "framework",
"language": "kg_lang_php",
"repository": "kg_repo_laravel_framework",
"website": "https://laravel.com"
}
}
Package
Status: Planned. Also a specialisation of today's live generic
technology type — a published, versioned package rather than the
source repository it may be built from (npm, PyPI, Go modules,
crates.io).
Fields
| Field | Type | Required | Description |
|---|---|---|---|
registry |
string | Yes | "npm", "pypi", "go_modules", "crates_io", or another free-form value. |
about |
string|null | No | Short description. |
latestVersion |
string|null | No | Latest published version, refreshed periodically. |
repository |
string|null | No | kg_id of the source Repository. |
JSON
{
"_type": "package",
"_id": "ent-pkg-chi",
"kg_id": "kg_pkg_go_chi",
"name": "github.com/go-chi/chi",
"confidence": 0.90,
"salience": 0.55,
"mentions": [{ "blockKey": "b5", "startChar": 8, "endChar": 30, "text": "github.com/go-chi/chi" }],
"metadata": {
"registry": "go_modules",
"latestVersion": "v5.0.12",
"repository": "kg_repo_chi"
}
}
API
Status: Planned. A publicly documented API a piece of content references — a REST or GraphQL API, not the client library that calls it (that is a Package).
Fields
| Field | Type | Required | Description |
|---|---|---|---|
about |
string|null | No | Short description. |
style |
string|null | No | "rest", "graphql", "grpc", "soap", or another free-form value. |
docsUrl |
string|null | No | Link to the API's documentation. |
provider |
string|null | No | kg_id of the providing Organisation. |
Cloud service
Status: Planned — its enrichment connector is built and in testing, so these fields are what the graph will hold once it ships. A managed cloud offering — AWS Lambda, Google BigQuery, Azure Functions — distinct from the Platform it runs on top of.
Fields
Filled from: Wikipedia and Wikidata, with a Wikidata search for services that have no Wikipedia page of their own.
| Field | Type | Required | Description |
|---|---|---|---|
provider |
object|null | No | { "name", "kg_id" } — the providing Organisation. |
category |
string|null | No | e.g. "serverless computing", "cloud storage". |
docs |
string|null | No | The service's documentation or product page. |
JSON
{
"_type": "cloud_service",
"_id": "ent-cloud-lambda",
"kg_id": "kg_cloud_aws_lambda",
"name": "AWS Lambda",
"confidence": 1.0,
"salience": 0.45,
"mentions": [{ "blockKey": "b4", "startChar": 22, "endChar": 32, "text": "AWS Lambda" }],
"metadata": {
"provider": { "name": "Amazon Web Services", "kg_id": "kg_org_aws" },
"category": "serverless computing",
"docs": "https://aws.amazon.com/lambda"
}
}
Platform
Status: Planned — its enrichment connector is built and in testing, so these fields are what the graph will hold once it ships. A broader compute or hosting platform — Kubernetes, Vercel, Heroku — that one or more Cloud services run on.
Fields
Filled from: Wikipedia and Wikidata. When the platform is its own
company (Vercel, Netlify), category is the company's industry and it
maintains itself.
| Field | Type | Required | Description |
|---|---|---|---|
category |
string|null | No | e.g. "cloud computing", "free and open-source software". |
website |
string|null | No | Official website. |
maintainedBy |
object|null | No | { "name", "kg_id" } — who builds it. |
JSON
{
"_type": "platform",
"_id": "ent-platform-k8s",
"kg_id": "kg_platform_kubernetes",
"name": "Kubernetes",
"confidence": 1.0,
"salience": 0.60,
"mentions": [{ "blockKey": "b4", "startChar": 19, "endChar": 29, "text": "Kubernetes" }],
"metadata": {
"category": "free and open-source software",
"website": "https://kubernetes.io",
"maintainedBy": { "name": "Google", "kg_id": "kg_org_google" }
}
}
CLI tool
Status: Planned — its enrichment connector is built and in
testing, so these fields are what the graph will hold once it ships.
A command-line tool as a thing in the world —
kubectl, terraform, jq — as distinct from a Package
you import.
Fields
Filled from: Homebrew's formula data, then Wikipedia and Wikidata for tools Homebrew doesn't package, plus the repository's stars from GitHub.
| Field | Type | Required | Description |
|---|---|---|---|
version |
string|null | No | Latest stable version. |
license |
string|null | No | Licence, SPDX where known, e.g. "MIT". |
website |
string|null | No | Official website. |
category |
string|null | No | e.g. "command-line interface"; only when it came from Wikidata. |
repository |
object|null | No | { "name", "stars", "kg_id" } — its source Repository. |
JSON
{
"_type": "cli_tool",
"_id": "ent-cli-jq",
"kg_id": "kg_cli_jq",
"name": "jq",
"confidence": 1.0,
"salience": 0.25,
"mentions": [{ "blockKey": "b5", "startChar": 61, "endChar": 63, "text": "jq" }],
"metadata": {
"version": "1.8.2",
"license": "MIT",
"website": "https://jqlang.github.io/jq/",
"repository": { "name": "jqlang/jq", "stars": 35802, "kg_id": "kg_repo_jq" }
}
}
Database
Status: Planned — its enrichment connector is built and in testing, so these fields are what the graph will hold once it ships. A database engine or product — PostgreSQL, Redis, DynamoDB.
Fields
Filled from: Wikipedia and Wikidata, with the current version from endoflife.date, which tracks releases more closely than Wikidata does.
| Field | Type | Required | Description |
|---|---|---|---|
category |
string|null | No | "relational", "document", "key_value", "graph", "search", or another value. |
license |
string|null | No | Licence name, e.g. "PostgreSQL License". |
version |
string|null | No | Latest release. |
website |
string|null | No | Official website. |
JSON
{
"_type": "database",
"_id": "ent-db-postgres",
"kg_id": "kg_db_postgresql",
"name": "PostgreSQL",
"confidence": 1.0,
"salience": 0.50,
"mentions": [{ "blockKey": "b6", "startChar": 22, "endChar": 32, "text": "PostgreSQL" }],
"metadata": {
"category": "relational",
"license": "PostgreSQL License",
"version": "18.6",
"website": "https://www.postgresql.org"
}
}
Protocol and standard
Status: Planned. A named protocol or technical standard — HTTP/2, OAuth 2.0, gRPC — as a concept, distinct from any RFC document that specifies it.
Fields
| Field | Type | Required | Description |
|---|---|---|---|
about |
string|null | No | Short description. |
specifiedBy |
array|null | No | kg_id list of the RFC or standards documents that define it. |
RFC
Status: Planned — its enrichment connector is in review (PR #429). A specification document — an IETF RFC, a W3C recommendation.
Fields
Filled from: the RFC Editor's record for the RFC number. The number
stays in the entity's name, e.g. "RFC 9110".
| Field | Type | Required | Description |
|---|---|---|---|
title |
string | Yes | Document title. |
publishedYear |
integer|null | No | Year published. |
status |
string|null | No | e.g. "INTERNET STANDARD", "PROPOSED STANDARD". |
specUrl |
string | Yes | Link to the document on rfc-editor.org. |
JSON
{
"_type": "rfc",
"_id": "ent-rfc-9110",
"kg_id": "kg_rfc_9110",
"name": "RFC 9110",
"confidence": 1.0,
"salience": 0.25,
"mentions": [{ "blockKey": "b3", "startChar": 40, "endChar": 48, "text": "RFC 9110" }],
"metadata": {
"title": "HTTP Semantics",
"publishedYear": 2022,
"status": "INTERNET STANDARD",
"specUrl": "https://www.rfc-editor.org/rfc/rfc9110"
}
}
Article
Status: Planned — its enrichment connector is built and in testing, so these fields are what the graph will hold once it ships. Renamed from the "blog post" entry on the roadmap to cover any standalone published piece — a blog post, a news item, a tutorial — that is not part of a Book or presented at a Conference.
Fields
Filled from: the article's own page — the preview tags publishers set
for link sharing. The article's title becomes the entity's name.
Pages that are gone, or that block automated readers, are not found.
| Field | Type | Required | Description |
|---|---|---|---|
url |
string | Yes | The article's canonical link. |
category |
string|null | No | The publisher's section, e.g. "blog", "article". |
publisher |
object|null | No | { "name", "kg_id" } — the publication or site. |
JSON
{
"_type": "article",
"_id": "ent-article-microservices",
"kg_id": "kg_article_martinfowler_microservices",
"name": "Microservices",
"confidence": 0.95,
"salience": 0.20,
"mentions": [{ "blockKey": "b2", "startChar": 31, "endChar": 82, "text": "https://martinfowler.com/articles/microservices.html" }],
"metadata": {
"url": "https://martinfowler.com/articles/microservices.html",
"category": "article",
"publisher": { "name": "martinfowler.com", "kg_id": null }
}
}
Citation
Status: Planned — its enrichment connector is built and in
testing, so these fields are what the graph will hold once it ships.
A structured bibliographic reference an entity
detector spots in text — distinct from the citation annotation
type in PCF, which is authored directly
by an editor. This entity is what enrichment produces when it
recognises a citation-shaped mention and resolves what it points to.
Today detection recognises citations by their DOI.
The field that matters most: resolvesToContent links to the actual
work in the Content Lake, when the cited work is itself a Packt
Content Unit —
rather than materialising a synthetic, disconnected "paper" node for
something the platform already holds natively.
Fields
Filled from: Crossref by DOI, then DataCite for DOIs Crossref doesn't
hold (arXiv, Zenodo). The work's title becomes the entity's name.
| Field | Type | Required | Description |
|---|---|---|---|
doi |
string | Yes | Digital Object Identifier. |
authors |
array|null | No | Author names, as published. |
year |
integer|null | No | Year published. |
resolvesToContent |
string|null | No | A cl:// URI, when the cited work is a Packt Content Unit. Set when results are merged, not by the connector. |
JSON
{
"_type": "citation",
"_id": "ent-cite-optuna",
"kg_id": "kg_cite_10_1145_3292500_3330701",
"name": "Optuna",
"confidence": 0.95,
"salience": 0.20,
"mentions": [{ "blockKey": "b9", "startChar": 3, "endChar": 26, "text": "10.1145/3292500.3330701" }],
"metadata": {
"doi": "10.1145/3292500.3330701",
"authors": ["Takuya Akiba", "Shotaro Sano", "Toshihiko Yanase", "Takeru Ohta", "Masanori Koyama"],
"year": 2019
}
}
Conference
Status: Planned. A single, dated instance of a conference — PHP Con 2024, KubeCon EU 2025. The recurring series (PHP Con, KubeCon) is not tracked as its own type: searching by name already groups every year's instance together.
Fields
| Field | Type | Required | Description |
|---|---|---|---|
startDate |
string|null | No | ISO 8601 start date. |
endDate |
string|null | No | ISO 8601 end date. |
location |
string|null | No | City/venue. |
Book
Status: Planned — its enrichment connector is built and in
testing, so these fields are what the graph will hold once it ships.
A single published book, found by its ISBN.
Each edition is its own book; series such as the yearly CompSci
editions are not a separate type, since search by name already groups
them.
Fields
Filled from: Open Library by ISBN, then Google Books when an API key
is set. The book's title becomes the entity's name.
| Field | Type | Required | Description |
|---|---|---|---|
isbn |
string | Yes | ISBN as written, e.g. "978-0-13-419044-0". |
edition |
string|null | No | Edition label, e.g. "3rd", where published. |
publisher |
object|null | No | { "name", "kg_id" } — the publishing Organisation. |
rating |
number|null | No | Average reader rating out of 5, where readers have rated it. |
JSON
{
"_type": "book",
"_id": "ent-book-gopl",
"kg_id": "kg_book_9780134190440",
"name": "The Go Programming Language",
"confidence": 1.0,
"salience": 0.30,
"mentions": [{ "blockKey": "b7", "startChar": 70, "endChar": 92, "text": "ISBN 978-0-13-419044-0" }],
"metadata": {
"isbn": "978-0-13-419044-0",
"publisher": { "name": "Addison-Wesley", "kg_id": "kg_org_addison_wesley" },
"rating": 4.4
}
}
Legal
Status: Planned — its enrichment connector is built and in testing, so these fields are what the graph will hold once it ships. A named law, regulation, or one article of it — GDPR Article 17, the EU AI Act. Low priority until legal content enters scope.
Fields
Filled from: Wikipedia and Wikidata. EU law links to its official text on EUR-Lex. "GDPR Article 17" is looked up as the GDPR and keeps the article in its name.
| Field | Type | Required | Description |
|---|---|---|---|
jurisdiction |
string|null | No | Where it applies, e.g. "EU", "UK", "US". |
effectiveDate |
string|null | No | ISO 8601 date it took effect. |
url |
string | Yes | Link to the official text, or its Wikipedia page if none. |
JSON
{
"_type": "legal",
"_id": "ent-legal-gdpr-17",
"kg_id": "kg_legal_gdpr_art17",
"name": "General Data Protection Regulation, Article 17",
"confidence": 0.90,
"salience": 0.30,
"mentions": [{ "blockKey": "b1", "startChar": 15, "endChar": 30, "text": "GDPR Article 17" }],
"metadata": {
"jurisdiction": "EU",
"effectiveDate": "2018-05-25",
"url": "https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32016R0679"
}
}
Licence (attribute)
Status: Planned. Not an independent node — a licence identifier
nested in the metadata of whatever it licenses (a
Repository, a Package). Represented as an
SPDX identifier string, e.g. "MIT", "Apache-2.0". See
repository.metadata.license for a worked example.
Excluded: email
Email addresses are deliberately not a supported Social profile type, on GDPR grounds — an email address is direct personal contact information, not a public profile link, and detecting and storing it as graph metadata creates exposure the other profile types do not.
Under review
The following are recognised as plausible future types but do not yet have a settled shape, and are listed here so this catalogue reflects what is actively being thought about, not just what is decided:
- Algorithm — a named algorithm (e.g. Raft, Dijkstra's) as a concept independent of any implementation.
- Design pattern — a named software design pattern (e.g. Singleton, Observer).
- Security concept — a named vulnerability class or security concept (e.g. SQL injection, zero-trust).
Nested entities in larger objects
A node's metadata can embed other nodes' kg_id values as
cross-references — Repository's languages array,
Framework's repository field — rather than
duplicating their data. Resolving "Laravel" this way can surface its
organisation, its primary language, and its source repository from one
entity, each still independently addressable by its own kg_id.
Requesting a new type or field
The types marked Planned and Under review on this page are not commitments with a ship date — they are the current design direction, shared here so the org can plan around it and give feedback before it is built. If your work needs one of these sooner, needs a type not listed at all, or needs a new field on an existing type, raise it via the Tech Hub channel in Microsoft Teams, or email tech@packtpub.com. Prioritisation follows demand.
Related pages
- Enrichment & the Knowledge Graph — the friendly, business-level overview this page is the exhaustive counterpart to.
- The content format and
PCF reference — the block-and-span structure the
entity overlay addresses by
_keyand character range. - Search — finding content by the entities it mentions.
- Glossary — one-line definitions for Knowledge Graph, entity, and overlay.