Knowledge Graph Enhancement with LLMs for Content Understanding

netflix · Media & Entertainment · year n/a · source Agentic: no · promotional bias: low · source-backed · extracted with prompt 0.5.6 (schema v2)

Generated from extraction.json — do not edit by hand. Every claim cites verbatim source evidence; stated means the quote directly asserts the claim, implied means it supports it indirectly.

Problem

Domain: Entertainment content knowledge graph

Netflix needed to enrich and maintain a large entertainment knowledge graph by matching entities at massive scale and extracting relationships not explicitly present in source data.

Constraints:

Architecture

Netflix uses Metaflow to orchestrate large-scale entity matching and is exploring RAG plus in-context learning to infer entity types and relationships from unstructured content.

Diagram confidence: reconstructed (reconstructed from prose).

flowchart LR
  entertainment-source-data["Entertainment Source Data"]
  metaflow-entity-matching["Metaflow Entity Matching"]
  apache-arrow-loading["Apache Arrow Loading"]
  llm-relationship-inference["LLM Relationship Inference"]
  knowledge-graph["Knowledge Graph"]
  entertainment-source-data --> metaflow-entity-matching
  metaflow-entity-matching --> apache-arrow-loading
  metaflow-entity-matching --> knowledge-graph
  apache-arrow-loading --> metaflow-entity-matching
  llm-relationship-inference --> knowledge-graph
Drag to pan · scroll or use +/− to zoom · reconstructed from the source's described component topology

Components

Component Role Interacts with
Entertainment Source Data Provides content entities and unstructured relationship evidence. Metaflow Entity Matching
Metaflow Entity Matching Orchestrates distributed matching over billions of entity pairs. Apache Arrow Loading, Knowledge Graph
Apache Arrow Loading Accelerates large-scale data loading for matching jobs. Metaflow Entity Matching
LLM Relationship Inference Uses RAG and in-context learning to infer entity types and relationships. Knowledge Graph
Knowledge Graph Stores enriched entertainment entities and relationships. —

Data flow

Entertainment data flows into Metaflow-orchestrated distributed jobs for entity matching, fast Apache Arrow loading accelerates pair processing, and newer LLM/RAG pipelines infer semantic types and relationships from unstructured content.

“using Metaflow to orchestrate billions of entity matching pairs across distributed infrastructure.”summary, stated
“using RAG pipelines and in-context learning to extract semantic relationships that weren't explicitly available in the source data”summary, stated

Why this architecture

Metaflow provides distributed orchestration and stability for massive matching, while LLM/RAG inference targets semantic relationships unavailable in structured source fields.

“maintaining production stability through Metaflow's namespacing and branching features.”summary, stated
“semantic relationships that weren't explicitly available in the source data”summary, stated

Models used: LLMs · RAG pipelines · Metaflow · Apache Arrow

Scale

Alternatives considered (roads not taken)

Explicit source-data relationships only

Rejected because: Some semantic relationships are not explicitly available in the source data.

“semantic relationships that weren't explicitly available in the source data”summary, stated

Ad hoc distributed jobs without Metaflow isolation

Rejected because: Production stability required namespacing and branching features.

“maintaining production stability through Metaflow's namespacing and branching features.”summary, stated

Patterns

rag-retrieval (retrieval)

Netflix uses RAG pipelines to support LLM relationship extraction from unstructured content.

“using RAG pipelines and in-context learning to extract semantic relationships”summary, stated

durable-execution (workflow)

Metaflow orchestrates massive distributed entity-matching jobs with production namespacing and branching.

“using Metaflow to orchestrate billions of entity matching pairs across distributed infrastructure.”summary, stated

Tradeoffs

Use Metaflow orchestration

Chose Namespaced and branched distributed pipelines over Unmanaged distributed matching scripts.

Rationale: The production graph required stability while running enormous matching jobs.

“maintaining production stability through Metaflow's namespacing and branching features.”summary, stated

Add LLM inference to graph enrichment

Chose RAG and in-context learning over Only explicit structured relationships.

Rationale: LLMs can infer semantic relationships not directly present in the source data.

“extract semantic relationships that weren't explicitly available in the source data”summary, stated

Gotchas (what bit them)

Knowledge graph enrichment can require relationships absent from source schemas.

Root cause: Unstructured content encodes semantic relationships implicitly.

Resolution: Explore LLM/RAG in-context inference to extract entity types and relationships.

“inferring entity types and relationships from unstructured content”summary, stated

Large-scale entity matching is bottlenecked by data loading.

Root cause: Billions of pair comparisons stress distributed IO.

Resolution: Use Apache Arrow fast loading for a 10x speedup.

“10x speedups through fast data loading with Apache Arrow.”summary, stated

Evaluation

The summary reports system speedup and production-stability practices but does not give relationship-extraction accuracy metrics.

Metrics: Entity-matching speedup · Distributed pipeline stability

“achieving 10x speedups through fast data loading with Apache Arrow.”summary, stated

Outcomes

The knowledge graph workflow operates over billions of entity-matching pairs.

“The system enables entity matching at scale through parallel processing”summary, stated