Skip to content

Blockmodel

A reduced network representation that groups nodes into positions and summarizes ties within and between those groups as blocks.

Version
v1 · 2026-09-28 · History
Domain-specific #
8232
Domain group
Social Sciences
Origin domain
Sociology & Anthropology
Subdomains
Social Network Analysis, Blockmodeling → Sociology & Anthropology
Aliases
Block model

Core Idea

A blockmodel is the position-level object produced when a network is compressed by relational pattern. First the vertices are assigned to positions according to a declared equivalence or fitting criterion. Then ties within and between positions are represented as blocks, commonly visible as submatrices of a reordered adjacency matrix. The reduced image records how positions relate, making a large network's role structure easier to inspect.

The output should not be confused with blockmodeling, the family of procedures that constructs or fits it. Nor is every community partition already a blockmodel; relational blocks must be represented. Choice of structural versus regular equivalence, deterministic versus stochastic fit, and treatment of missing or noisy ties can change the image. An employee knowledge-flow study supplies an actual use, but its position labels remain interpretations of observed relations, not an identity assigned to every person independent of the network.

How would you explain it like I'm…

The Tiny Who-Talks Map

Imagine a huge map of who talks to whom in a big school. A blockmodel groups the people who have the same kind of connections, like "people who help others" and "people who ask for help," and then draws a tiny map showing how those groups connect. It makes a giant tangle of friendships easy to read.

Groups by How People Connect

A network is a set of people (or things) and the links between them, like who gives advice to whom. A blockmodel is a simplified picture of such a network. First, people are sorted into groups, called positions, based on having similar patterns of links. Then the links inside and between groups are shown as blocks, and a small summary shows how the positions relate, for example "managers send information to workers." A blockmodel is the finished summary, not the steps used to make it. The group names are interpretations of the links that were seen, not fixed labels stuck on each person.

Position-Level Network Image

A blockmodel is the simplified, position-level picture of a network produced by grouping nodes according to their pattern of relationships. Nodes are assigned to positions using a stated equivalence or fitting rule, and ties within and between positions are then represented as blocks, often seen as submatrices when the adjacency matrix is reordered by position. The resulting reduced "image" shows how positions relate, making a big network's role structure easier to understand. A blockmodel is the output; blockmodeling is the set of methods that build or fit it. Not every community partition counts as a blockmodel, because the relations between blocks must be represented. Choices such as structural versus regular equivalence, deterministic versus stochastic fitting, and how missing or noisy ties are handled can change the result, and position labels are interpretations of observed relations.

 

A blockmodel is the position-level object produced by compressing a network according to relational pattern. Vertices are first assigned to positions under a declared equivalence or fitting criterion, for example structural equivalence, regular equivalence, or a stochastic model fit. Ties within and between positions are then represented as blocks, typically visible as submatrices of the adjacency matrix after reordering rows and columns by position. The reduced image matrix records how positions relate, exposing the network's role structure. The blockmodel is distinct from blockmodeling, the family of procedures that construct or fit it, and distinct from a community partition, which becomes a blockmodel only when relational blocks are represented. The resulting image depends on analytic choices: structural versus regular equivalence, deterministic versus stochastic fitting, and how missing or noisy ties are handled. In an application such as an employee knowledge-flow study, position labels are interpretations of observed relations rather than identities assigned to people independent of the network.

Scope of Application

These uses concern a reduced relational network object, not its fitting algorithm.

  • Social-network analysis. Represent positions and their between-group ties.
  • Organizational knowledge flow. Compare cohesive and core–periphery structures in observed networks.
  • Method comparison. Inspect how equivalence criteria change the same network's model.
  • Model criticism. Trace what actor-level ties a blockimage omits.

Clarity

Specify the source network, position grouping rule, within- and between-group tie blocks, and reduced image. A list of communities is the closest miss: it groups nodes without representing their relational blocks. A raw adjacency matrix has ties but not position-level reduction. Structural and regular equivalence can yield different images; role names depend on the chosen fit and observed ties rather than inhering permanently in people.

Manages Complexity

A blockmodel turns many individual ties into a smaller matrix of position relations, revealing broad patterns without scanning every edge. This can make comparisons possible while hiding exceptions, sampling errors, and criterion sensitivity; the compact image must remain linked to the source network and fit assumptions.

Abstract Reasoning

  1. Identify the vertices and measured relation type.
  2. State whether positions use structural, regular, stochastic, or another criterion.
  3. Group vertices and identify the resulting within/between submatrices.
  4. Build the reduced position-level tie image.
  5. Check residual ties and sensitivity before naming social roles or consequences.

Knowledge Transfer

The node-position-block-image relation transfers among friendship, collaboration, and knowledge-flow networks if each supplies its own relation and fit criterion. A specific employee core–periphery interpretation cannot be imposed on another network; clustering without block ties is not enough.

Relationships to Other Abstractions

Local relationship map for BlockmodelParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.BlockmodelDOMAINPrime abstraction: Representation — is a kind ofRepresentationPRIME

Current abstraction Blockmodel Domain-specific

Parents (1) — more general patterns this builds on

  • Blockmodel is a kind of Representation Prime

    A blockmodel maps a detailed network into a position-and-block medium, preserving selected tie patterns for interpretation while omitting actor-level detail.

Hierarchy path (1) — routes to 1 parentless root

Neighborhood in Abstraction Space

Blockmodel sits in a crowded region of the domain-specific corpus (37th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Graph Structures & Algorithms (24 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-08