```json { "table_name": "analysis_runs", "primary_key": "jobs_id", "candidates": [ { "rank": 0, "partition_key": "jobs_id", "partition_key_label": "primary_identifier", "partition_key_reasoning": "jobs_id is the unique identifier with RPUV=1.00, uniqueness=1.000, and 116 distinct values matching row count. It serves as the natural primary key for this dimension table tracking analysis run metadata.", "clustering_key": null, "clustering_key_label": null, "clustering_key_reasoning": "Dimension tables typically do not require clustering keys as they are lookup tables organized by their primary identifier.", "world_line": null, "session_column": null, "confidence": "HIGH", "notes": "This is a dimension table cataloging analysis runs. The entity_columns classification correctly identifies jobs_id as the primary identifier. Alternative candidate internal_run_id also has RPUV=1.00 but jobs_id is the semantic business key. Many columns have 100% null values (report_id, intent, code_version, dataset_version_hash, analysis_config_json, error_text), suggesting this may be a partially populated metadata table. The _ingestion_timestamp, _batch_id, _source_file, and _source_system columns are ETL metadata, not business dimensions." } ] } ```