PHPMem v2.0.1
Version
1.6.45
Uptime
15 days 9 hours 30 minutes 27 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
11 / 1 024 max
Total
170 544
Rejected
0
llm:2e25d74273428551fddb79e92a7d2dc74588b0109975b5c8f56da2b63217f5da
Edit
```json
{
"table_name": "2018_WEEK 12_plays",
"table_type_tags": [
{"tag": "event", "confidence": 0.90},
{"tag": "path", "confidence": 0.15}
],
"primary_type": "event",
"insufficient_evidence": false,
"entity": {
"columns": ["AwayTeam", "HomeTeam", "TeamWithPossession", "DriveNumber"],
"unique_per_row": false
},
"time_axis": {
"columns": ["PlayNumberInDrive"],
"kind": "sequence"
},
"reasoning": "The entity is the composite (TeamWithPossession, DriveNumber) — a team's drive within the week's games — which repeats across rows (TeamWithPossession RPUV 82.77, DriveNumber RPUV 248.30). PlayNumberInDrive is a sequence counter (Monotonicity 0.868) ordering plays within each drive. A row exists because a play HAPPENED — the PlayOutcome and PlayDescription record discrete actions (passes, runs, kicks, penalties). Replaying the plays does not reconstruct a meaningful drive state (no cumulative yardage or down-and-distance balance tracked row-to-row); the rows are bare occurrences to count and analyze → event. The weak path signal comes from the sequential structure, but the lack of state-derivability keeps event dominant."
}
```