Category Taxonomy Regime Hierarchy

Purpose: Define how to read Wikipedia's category system as a native regime hierarchy — a massive, community‑maintained classification tree that organizes 6.9 million English articles into nested regime boundaries.

Wikipedia's category tree is not a controlled taxonomy designed by information scientists. It is a crowdsourced, evolving regime map — built by thousands of editors making local classification decisions that aggregate into a global structural hierarchy. This makes it messy, contradictory in places, and deeply revealing of how humans actually organize knowledge.

Where Wikidata provides dimensional addressing (unique identifiers), the category tree provides regime topology (where a concept sits relative to all other concepts).

1 — What Is a Wikipedia Category?#

Every Wikipedia article is assigned to one or more categories — classification labels that place the article within a hierarchical tree of related concepts.

How Categories Work#

How to Access Categories#

2 — The Category Tree as Regime Hierarchy#

2.1 — Structural Anatomy#

Wikipedia's category system forms a directed acyclic graph (DAG) — not a strict tree. Categories can have multiple parents, creating a web of overlapping regime boundaries:

                    Category:Main topic classifications
                    (root regime — R0)
                           │
          ┌────────────────┼────────────────┐
          │                │                │
    Category:Science  Category:Society  Category:Technology
    (domain regime)   (domain regime)   (domain regime)
          │                │                │
    ┌─────┴─────┐    ┌────┴────┐     ┌────┴────┐
    │           │    │         │     │         │
  Cat:Physics Cat:Bio Cat:Politics Cat:Law Cat:Computing Cat:Eng
    │           │         │              │
  Cat:Quantum Cat:Genetics Cat:Elections Cat:Programming
  mechanics                                  │
    │                              ┌─────────┴─────────┐
    │                              │                   │
  Cat:Quantum  ←── cross‑link ──→ Cat:Quantum
  mechanics                       computing

2.2 — The DAG Problem#

Because categories form a DAG (not a tree), the same article can be reached by multiple paths from the root. This is not a bug — it reflects the reality that concepts belong to multiple regimes simultaneously:

RTT reading: Multiple category paths = multiple regime memberships. The number of distinct paths from root to an article = the concept's regime multiplicity. Concepts with high multiplicity sit at regime intersections — they are structurally significant because multiple classification systems claim them.

2.3 — Depth and Breadth#

Two key metrics characterize any position in the category hierarchy:

3 — Category Types and Their Regime Functions#

3.1 — The Six Category Types#

3.2 — By‑Attribute Categories as Regime Faceting#

By‑attribute categories are structurally special — they slice a domain regime by an external dimension, revealing how the regime varies across that dimension:

RTT reading: By‑attribute categories are regime cross‑sections — they show how a single domain regime manifests differently when sliced along an external dimension. The existence of a by‑attribute category means the community considers that dimension structurally significant for that domain.

4 — The Category Tree vs. Wikidata Class Hierarchy#

Wikipedia has two parallel classification systems:

Key Insight: These Systems Disagree#

For any given concept, its Wikipedia category path and its Wikidata class hierarchy may tell different stories:

RTT reading: Category tree = how the community organizes knowledge (cultural, editorial, pragmatic). Wikidata = how entities are formally classified (ontological, structured, cross‑cultural). Disagreements between them reveal regime framing differences — the same concept declared differently depending on whether the classification is community‑editorial or ontologically formal.

5 — Structural Pathologies in the Category Tree#

The category tree is crowdsourced and evolving, which means it contains structural pathologies that are themselves regime signals:

5.1 — Overcategorization#

What it is: An article assigned to 20+ categories, many of which are semantically overlapping.

Regime reading: The concept has regime sprawl — it has been claimed by too many classification systems without consolidation. Overcategorized articles often sit at regime intersections where no single domain has primary ownership.

5.2 — Undercategorization#

What it is: An article assigned to only 1–2 very broad categories, with no subcategory refinement.

Regime reading: The concept has regime isolation — it hasn't been claimed by a stewardship group. Often indicates a neglected or newly created article that no WikiProject has adopted.

5.3 — Category Cycles#

What it is: Category A contains subcategory B, which contains subcategory C, which contains subcategory A — a circular reference.

Regime reading: Regime hierarchy failure — the classification system cannot decide which concept is more general. These are rare (Wikipedia has bots that detect them) but structurally revealing when they occur — they mark genuine ontological ambiguity.

5.4 — Orphan Categories#

What it is: A category with no parent categories (disconnected from the main tree).

Regime reading: Unmoored regime — a classification that exists but is not connected to the broader knowledge structure. Often indicates a recently created or poorly maintained category.

5.5 — Eponymous Categories#

What it is: A category named after a person (Category:Albert Einstein, Category:Works by Aristotle).

Regime reading: Person‑as‑regime — the community considers this individual's work, influence, or legacy significant enough to constitute its own classification node. The category's subcategories reveal how the community structures that person's regime (works, influences, legacy, biographical details).

6 — API Patterns for Category Analysis#

6.1 — Get an Article's Categories#

import requests
 
def get_categories(title, lang="en"):
    """Fetch all categories for a Wikipedia article."""
    url = f"https://{lang}.wikipedia.org/w/api.php"
    params = {
        "action": "query",
        "titles": title,
        "prop": "categories",
        "cllimit": "max",
        "clshow": "!hidden",  # exclude maintenance categories
        "format": "json"
    }
    resp = requests.get(url, params=params,
                        headers={"User-Agent": "TriadicFrameworks/1.0"}).json()
    page = next(iter(resp["query"]["pages"].values()))
    return [cat["title"].replace("Category:", "")
            for cat in page.get("categories", [])]

6.2 — Traverse the Category Tree Upward#

def trace_to_root(category, lang="en", max_depth=15):
    """Trace a category upward through parent categories toward root."""
    url = f"https://{lang}.wikipedia.org/w/api.php"
    path = []
    current = category
    visited = set()
 
    for depth in range(max_depth):
        if current in visited:
            break  # cycle detection
        visited.add(current)
 
        params = {
            "action": "query",
            "titles": f"Category:{current}",
            "prop": "categories",
            "cllimit": "max",
            "clshow": "!hidden",
            "format": "json"
        }
        resp = requests.get(url, params=params,
                            headers={"User-Agent": "TriadicFrameworks/1.0"}).json()
        page = next(iter(resp["query"]["pages"].values()))
        parents = [cat["title"].replace("Category:", "")
                   for cat in page.get("categories", [])]
 
        path.append({
            "depth": depth,
            "category": current,
            "parents": parents
        })
 
        if not parents or "Contents" in parents[0]:
            break  # reached root
        current = parents[0]  # follow first parent
 
    return path

6.3 — Get Subcategories and Membership Count#

def get_subcategories(category, lang="en"):
    """Fetch subcategories and article count for a category."""
    url = f"https://{lang}.wikipedia.org/w/api.php"
    params = {
        "action": "query",
        "list": "categorymembers",
        "cmtitle": f"Category:{category}",
        "cmtype": "subcat",
        "cmlimit": "max",
        "format": "json"
    }
    resp = requests.get(url, params=params,
                        headers={"User-Agent": "TriadicFrameworks/1.0"}).json()
    subcats = [m["title"].replace("Category:", "")
               for m in resp["query"]["categorymembers"]]
 
    # Also get article count
    params["cmtype"] = "page"
    resp2 = requests.get(url, params=params,
                         headers={"User-Agent": "TriadicFrameworks/1.0"}).json()
    articles = len(resp2["query"]["categorymembers"])
 
    return {
        "category": category,
        "subcategory_count": len(subcats),
        "subcategories": subcats,
        "article_count": articles
    }

6.4 — Compute Regime Topology Metrics#

def regime_topology(title, lang="en"):
    """Compute regime topology metrics for an article."""
    categories = get_categories(title, lang)
 
    # Depth: trace each category to root, take the longest path
    max_depth = 0
    all_paths = []
    for cat in categories[:5]:  # sample first 5 to avoid rate limits
        path = trace_to_root(cat, lang)
        depth = len(path)
        max_depth = max(max_depth, depth)
        all_paths.append(path)
 
    return {
        "article": title,
        "category_count": len(categories),
        "categories": categories,
        "max_depth": max_depth,
        "regime_multiplicity": len(categories),
        "deepest_path": all_paths[0] if all_paths else [],
        "interpretation": classify_topology(len(categories), max_depth)
    }
 
def classify_topology(cat_count, max_depth):
    """Classify an article's regime topology."""
    if cat_count <= 2 and max_depth <= 3:
        return "isolated_regime"
    elif cat_count <= 5 and max_depth <= 6:
        return "well_classified"
    elif cat_count <= 10 and max_depth <= 10:
        return "cross_domain_concept"
    elif cat_count > 15:
        return "regime_sprawl"
    else:
        return "deeply_specialized"

6.5 — Cross‑Language Category Comparison#

def compare_categories_cross_language(wikidata_qid, languages=None):
    """Compare category assignments for the same concept across languages."""
    if languages is None:
        languages = ["en", "de", "ja", "ar", "es"]
 
    url = "https://www.wikidata.org/w/api.php"
    params = {
        "action": "wbgetentities",
        "ids": wikidata_qid,
        "props": "sitelinks",
        "format": "json"
    }
    resp = requests.get(url, params=params,
                        headers={"User-Agent": "TriadicFrameworks/1.0"}).json()
    sitelinks = resp["entities"][wikidata_qid].get("sitelinks", {})
 
    results = {}
    for lang in languages:
        wiki_key = f"{lang}wiki"
        if wiki_key in sitelinks:
            title = sitelinks[wiki_key]["title"]
            cats = get_categories(title, lang)
            results[lang] = {
                "title": title,
                "category_count": len(cats),
                "categories": cats
            }
 
    return results

7 — Worked Example: "Energy"#

The concept Energy sits at one of the deepest regime intersections in Wikipedia's category tree.

Category Memberships (English Wikipedia)#

Regime Topology Analysis#

• Category count: 8+ (high → cross‑domain concept)
• Max depth: 6 (moderately specialized)
• Fan‑in: 3+ domain regimes claim it (Physics, Economics, Political Science)
• Regime multiplicity: Very high — Energy is one of the most cross‑domain concepts on Wikipedia
• Classification: cross_domain_concept with elements of regime_sprawl

Comparing Wikipedia Categories vs. Wikidata#

Divergence: Wikipedia's category tree routes Energy through both Physics AND Economics AND Policy — reflecting its multi‑regime nature. Wikidata's class hierarchy routes it strictly through Physics → Physical quantity — reflecting a more ontologically narrow classification.

RTT reading: Wikipedia's category tree is more regime‑honest for cross‑domain concepts like Energy because it preserves multiple regime memberships. Wikidata's P31/P279 chain is more ontologically precise but loses the cross‑domain richness.

Cross‑Language Category Comparison#

Insight: The Japanese Wikipedia categorizes Energy under a philosophical concept that has no equivalent in the English category tree — revealing a cultural regime frame that Western categorization misses entirely.

8 — The Category Tree as a Research Instrument#

8.1 — Regime Boundary Detection#

Categories mark where one regime ends and another begins. The boundary is visible where:

• A category has subcategories belonging to different WikiProjects
• An article belongs to categories from multiple domain regimes
• A category's talk page has disputes about what belongs in it

8.2 — Knowledge Gap Detection#

Missing or underpopulated categories reveal regime gaps — areas where Wikipedia's structural coverage is incomplete:

8.3 — Regime Evolution Tracking#

Category changes in an article's revision history reveal regime reclassification events:

def find_category_changes(title, lang="en"):
    """Find revisions that changed an article's categories."""
    url = f"https://{lang}.wikipedia.org/w/api.php"
    params = {
        "action": "query",
        "titles": title,
        "prop": "revisions",
        "rvlimit": "50",
        "rvprop": "ids|timestamp|comment|user",
        "format": "json"
    }
    resp = requests.get(url, params=params,
                        headers={"User-Agent": "TriadicFrameworks/1.0"}).json()
    page = next(iter(resp["query"]["pages"].values()))
 
    cat_changes = []
    for rev in page.get("revisions", []):
        comment = rev.get("comment", "").lower()
        if any(kw in comment for kw in
               ["category", "cat", "recat", "recategoriz", "reclassif"]):
            cat_changes.append({
                "rev_id": rev["revid"],
                "timestamp": rev["timestamp"],
                "user": rev.get("user", "anonymous"),
                "comment": rev.get("comment", "")
            })
 
    return cat_changes

RTT reading: Every category change is a regime reclassification event — the community has decided that this concept belongs to a different regime neighborhood than before. Tracking these changes over time reveals the concept's regime migration history.

9 — PetScan: Advanced Category Intersection Queries#

PetScan (https://petscan.wmcloud.org/) is a powerful tool for querying category intersections — finding articles that belong to multiple categories simultaneously:

9.1 — Use Cases for Regime Analysis#

9.2 — Example: Finding Cross‑Domain Concepts#

To find articles that are classified under both Physics and Philosophy:

1. Go to https://petscan.wmcloud.org/
2. Set Categories: Physics and Philosophy
3. Set Combination: Intersection (AND)
4. Set Depth: 3 (search 3 levels deep into subcategories)
5. Run query

Result: Articles like "Entropy," "Causality," "Determinism," "Quantum mechanics interpretations" — concepts that sit at the Physics↔Philosophy regime boundary.

RTT reading: These intersection results are the regime boundary population — the set of concepts that both domains claim. The size and composition of this population reveals how structurally connected the two domains are.

10 — Cross‑Reference to Other Module Files#

11 — Student Exercises#

Exercise 1 — Category Path Tracing (15 minutes)#

1. Pick any Wikipedia article
2. Scroll to the bottom and find its categories
3. Click one category and trace it upward through parent categories until you reach "Main topic classifications" or "Contents"
4. Count the depth (number of levels)
5. Go back and try a different category for the same article — does it reach the root through a different domain?
6. Write one sentence: "This article reaches the root via [path 1: N levels through Domain X] and [path 2: M levels through Domain Y]. It has a regime multiplicity of [number of top‑level categories]."

Exercise 2 — Cross‑Domain Intersection (20 minutes)#

1. Go to PetScan (https://petscan.wmcloud.org/)
2. Pick two domains you find interesting (e.g., Biology and Economics, or Physics and Philosophy)
3. Run an intersection query with depth 2
4. Examine the results: what concepts sit at the boundary between these two domains?
5. Pick one result article and read its lead paragraph — does it acknowledge its cross‑domain nature?
6. Write two sentences: "The intersection of [Domain A] and [Domain B] contains [N] articles. The most structurally interesting is [article] because [reason]."

Exercise 3 — Category Pathology Hunting (20 minutes)#

1. Browse Wikipedia's category tree starting from Category:Main topic classifications
2. Look for one example of each pathology from Section 5:
   • An overcategorized article (15+ categories)
   • An undercategorized article (1–2 categories only)
   • An orphan category (hint: check Category:Orphaned categories)
   • An eponymous category (person‑as‑regime)
3. For each, write one sentence explaining what the pathology reveals about the concept's regime status

Exercise 4 — Cross‑Language Category Comparison (30 minutes)#

1. Pick a concept you expect to have cultural variance (try: Democracy, Tea, Football, or a religion)
2. Find the article in English + 2 other languages
3. For each language, list the categories at the bottom of the article
4. Compare: Are the categories structurally similar? Do different languages categorize the concept under different domains?
5. Answer: "The most striking category difference is [X]. This reveals that [language A] frames the concept as part of [regime], while [language B] frames it as part of [different regime]."

Exercise 5 — Regime Reclassification Detection (30 minutes)#

1. Pick an article for a concept that has been reclassified in real life (try: Pluto, a renamed country, a reclassified species, or a substance whose legal status changed)
2. Use the find_category_changes function from Section 8.3 (or manually search the revision history for "category" in edit summaries)
3. Identify when the category change happened and what categories were added/removed
4. Answer: "The article was reclassified from [old categories] to [new categories] on [date]. This reflects the real‑world regime transition of [event]. The category change [preceded / followed / coincided with] the article text update by [N days]."

This file is part of the Wikipedia Awareness Module in the TriadicFrameworks canon.