PHPMem v2.0.1
Version
1.6.45
Uptime
15 days 9 hours 58 minutes 34 seconds
Memory
Total
512MB
Used
24,01MB (4.69%)
Free
487,99MB
Keys
Current
27 650
Total (since start)
33 978
Evictions
0
Reclaimed
160
Expired Unfetched
0
Evicted Unfetched
0
Connections
Current
12 / 1 024 max
Total
171 027
Rejected
0
llm:47dcf0319d4be229500c0fb632ce3dd786cc4d1347f8ee9351616376e427f64f
Edit
```json
{
"table_name": "2020_WEEK 15_plays",
"table_type_tags": [
{"tag": "event", "confidence": 0.95},
{"tag": "path", "confidence": 0.30}
],
"primary_type": "event",
"insufficient_evidence": false,
"entity": {
"columns": ["Season", "Week", "AwayTeam", "HomeTeam", "DriveNumber", "TeamWithPossession"],
"unique_per_row": false
},
"time_axis": {
"columns": ["PlayNumberInDrive"],
"kind": "sequence"
},
"reasoning": "The composite entity (Season+Week+AwayTeam+HomeTeam+DriveNumber+TeamWithPossession) identifies a drive, which repeats across rows (DriveNumber RPUV 247.45). PlayNumberInDrive is a sequence counter (Monotonicity 0.874) ordering plays within each drive. A row exists because a play HAPPENED — the PlayOutcome and PlayDescription record discrete actions (passes, runs, kicks). These are bare occurrences to count and analyze; replaying them does not reconstruct a meaningful drive state (no cumulative yardage or down-and-distance balance tracked per row). The rows are action-driven occurrences ordered by sequence within a repeating container entity → event. Weak path signal from the sequential ordering, but no state derivability."
}
```