NEWVectors or files. Pick a path.Start →
    Search & Discovery
    8 min read
    Updated 2026-07-10

    What Concepts Exist in My Data That Nobody Has Labeled Yet?

    Some queries cannot be answered by keyword search, vector search, or RAG — because the user does not know the ontology ahead of time. How discovered taxonomies answer questions like 'how does this brand visually represent trust?' and 'what stereotypes recur across our advertising?' with six worked examples.

    Discovered Taxonomies
    Exploratory Search
    Clustering
    Brand Intelligence
    Corpus Understanding

    The Short Answer



    There is a class of queries that no conventional search system can answer: the ones where you do not know what you are looking for yet. Keyword search needs your term, vector search needs your example, and RAG needs your question — all three assume the ontology exists before the query does. Discovered taxonomies invert this: the system clusters the latent structure of your corpus first, labels what it finds, and hands you a navigable hierarchy — so the answer to "what concepts exist in my data?" is computed, not retrieved.

    Why do these queries break normal search?



    A concept like "trust" in advertising is not a keyword and not a single embedding neighborhood. It is expressed through hundreds of recurring motifs — handshakes, doctors, families, a certain palette, a certain pacing — that no one enumerated in advance. Any system that requires the query to name the target fails in one of two ways: it returns the literal matches (videos containing the word "trust") or it returns one neighborhood of one motif and misses the rest. The fix is structural: cluster the corpus across every modality (the mechanics of clustering across modalities — and clustering the clusterings — are in composite clustering), let the recurring motifs surface as groups, label the groups, and organize them into a taxonomy that emerged from the data (the inverse job — assigning content to a taxonomy you already have — is taxonomy classification) rather than a whiteboard.

    Six queries that require a discovered ontology



    1. "Show me how this company visually represents trust." A corpus of 500,000 marketing videos expresses "trust" through motifs nobody listed: handshakes, smiling clinicians, families at tables, steady wide shots. Clustering finds these as recurring visual groups; the taxonomy names them; the query becomes navigation.

    2. "Find every way our brand has portrayed fathers." Not the keyword "father" — the dad fixing a bike, the barbecue, the cheering at soccer, the hug at the door, the voiceover that says "Dad." No human enumerates that list beforehand; the corpus already contains it as structure.

    3. "What stereotypes keep appearing across our advertising?" Nobody knows the answer in advance — that is the point. The hierarchy surfaces clusters that were never labels: women cooking, elderly couples, military families. Emergent structure is the only honest answer to a question about patterns you have not noticed.

    4. "Show me the evolution of 'luxury' over the last 20 years." Luxury drifts: marble kitchens, then Teslas, then quiet-luxury minimalism. A concept with a moving definition cannot be a stored label — but time-sliced clusters over the same corpus reveal the drift directly.

    5. "Find content spiritually similar to this commercial." Not visually similar, not semantically similar — evoking the same nostalgia or anticipation without sharing objects, people, or words. Cross-modal cluster membership captures affinity that no single embedding distance expresses.

    6. "What themes exist in my footage that I don't know exist?" The purest form: not a search at all, but "teach me the ontology of my data." A query-first system cannot start; a structure-first system has already finished.

    How does the machinery actually work?



    The pipeline is embed, cluster, label, promote: every asset is decomposed into per-segment features (visual, transcript, faces, on-screen text), clustering groups the segments across feature spaces, an LLM labels each cluster from its actual contents, and stable clusters are promoted into a hierarchical taxonomy that then classifies new content at ingest, powers filters at query time, and reclassifies retroactively when the hierarchy changes. Every search and correction afterward sharpens the structure — the ontology compounds instead of decaying.

    Doing this on Mixpeek



    This loop is Mixpeek's core mechanism, not a feature bolted onto search: server-side clustering runs at collection scale over content in your own object storage, the Studio cluster explorer makes the groups browsable with real sample items, one step promotes a cluster to a taxonomy, and retrievers use the taxonomy as filters alongside every other signal. The brand-intelligence version of these six queries — trust motifs, brand portrayals, creative drift — is the Creative DNA solution. Start with how the compounding loop works or explore clustering.
    Managed Mixpeek

    Put multimodal search to work

    Connect a bucket and Mixpeek runs the whole multimodal search pipeline for you: extraction, indexing, and search over your own objects. No models to wire up, nothing to host.

    Start with Managed
    MVS · bring your own

    Already have vectors?

    Keep your embeddings on your own cloud and run dense, sparse, and BM25 search directly on object storage. From $25/mo.

    Start with MVS

    Run this on your own data

    Point Mixpeek at the storage you already have and search your video, images, audio, and documents the way this guide describes. Build starts at $25/mo for up to 1M vectors.

    Search your own archive, freeRead Docs

    Related guides

    Search & Discovery

    How Do AI Agents Search Big Datasets by Navigating Clusters? (Hierarchical Cluster Search)

    Flat vector search returns top-k against one query vector, which breaks down when an agent does not know the right query, the corpus is huge and diverse, or the task is exploratory. Agentic hierarchical cluster search gives the agent a map instead: a cluster hierarchy (themes -> sub-clusters -> records) it navigates coarse-to-fine, scoring its goal against a few dozen centroids and drilling into the matching branch before running a precise retrieval at the leaf. When it beats flat ANN, the navigation loop, the cost math, the honest limits, and how to build it from clustering + composite clustering + a cluster-scoped retriever.

    Read guide →
    Search & Discovery

    How Do I Automatically Classify Content Against a Taxonomy?

    Auto-classifying images, video, documents, and audio into predefined categories at scale: the four viable methods in 2026 (zero-shot, embedding-similarity, trained head, LLM) and when each wins, how taxonomy classification differs from discovered taxonomies and metadata extraction, classifying non-text content by decomposing signals, taxonomy design rules, and the query-time reclassification pattern that avoids re-paying analysis when categories change.

    Read guide →
    Search & Discovery

    How Do I Filter Vector Search Results by Location? (Radius, Bounding Box, Polygon)

    Filter vector-search and retriever results by geographic location with three operators in an attribute_filter stage — geo_radius (within N meters), geo_bounding_box, and geo_polygon. Exact request shapes, the lat/lon-vs-GeoJSON lon-first gotcha, when to use each operator, combining geo with semantic search and metadata for location-aware RAG, and honest scope (a precise scan over your retrieved set, not a planet-scale geo index).

    Read guide →