```json { "table_name": "quality_issues", "table_type_tags": [ {"tag": "dimension", "confidence": 0.75}, {"tag": "event", "confidence": 0.30} ], "primary_type": "dimension", "insufficient_evidence": false, "entity": { "columns": ["id"], "unique_per_row": true }, "time_axis": { "columns": [], "kind": null }, "reasoning": "The entity id has Uniqueness 1.000 and Monotonicity 1.000, making each row unique. The table catalogs quality issues detected during data profiling jobs — each issue is a distinct finding with its own ID. The _ingestion_timestamp is a provenance column (ignored per rules), leaving no usable time axis. The repeating jobs_id (RPUV 3.59) and dataset_id (RPUV 5.56) are references to parent entities (jobs and datasets), not a repeating entity within this table. With a unique entity per row and no event axis ordering actions, this is dimension — a catalog of detected issues. The weak event reading comes from the issue-detection context (issues are discovered occurrences), but without a natural timestamp ordering those discoveries, dimension dominates." } ```