```json { "table_name": "neal_probe_runs", "table_type_tags": [ {"tag": "dimension", "confidence": 0.90} ], "primary_type": "dimension", "insufficient_evidence": false, "entity": { "columns": ["id"], "unique_per_row": true }, "time_axis": { "columns": ["created_at", "started_at", "finished_at"], "kind": "event_time" }, "reasoning": "The entity id has Uniqueness 1.000 (RPUV 1.00), making each row unique information about one probe run. While created_at, started_at, and finished_at are event timestamps (all Uniqueness 1.000), they describe attributes of each probe run's lifecycle — when it was created, started, and finished — rather than ordering actions or state transitions of a repeating entity. The table catalogs probe run executions: each run is a distinct occurrence with its own unique identifier, and sibling tables (neal_findings, neal_readings, neal_actions) likely reference these runs. This is a catalog of occurrence-like things, making it dimension despite the timestamps." } ```