```json { "table_name": "jobs", "table_type_tags": [ {"tag": "dimension", "confidence": 0.95} ], "primary_type": "dimension", "insufficient_evidence": false, "entity": { "columns": ["job_id"], "unique_per_row": true }, "time_axis": { "columns": ["started_at", "finished_at", "created_at", "updated_at"], "kind": "event_time" }, "reasoning": "The entity job_id is unique per row (Uniqueness 1.000, RPUV 1.00), making each row a distinct job record. While the table contains multiple event timestamps (started_at, finished_at, created_at, updated_at), these are descriptive attributes of each job's lifecycle, not an axis ordering repeated occurrences of the same job. The data preview shows each job_id appears exactly once with its complete execution metadata (type, status, elapsed_ms, error_count). This is a catalog of job executions where each row defines one job occurrence — dimension." } ```