PHPMem v2.0.1

Version
1.6.45
Uptime
7 days 13 hours 49 minutes 11 seconds

Memory

Total
512MB
Used
13,33MB (2.6%)
Free
498,67MB

Keys

Current
10 166
Total (since start)
11 096
Evictions
0
Reclaimed
157
Expired Unfetched
0
Evicted Unfetched
0

Connections

Current
3 / 1 024 max
Total
69 157
Rejected
0
llm:e4288e5432a992d0f22f6a5b308d2af6f70f0aae2901c718fd22e683b13d409f
TTL 25 minutes 28 seconds Size 1,31KB Export
Edit
```json { "table_name": "boxing_aj", "table_type_tags": [ {"tag": "dimension", "confidence": 0.80}, {"tag": "event", "confidence": 0.30} ], "primary_type": "dimension", "insufficient_evidence": false, "entity": { "columns": ["MatchLink-href"], "unique_per_row": true }, "time_axis": { "columns": ["web-scraper-order"], "kind": "sequence" }, "reasoning": "MatchLink-href has Uniqueness 1.000, uniquely identifying each bout. The web-scraper-order column (Uniqueness 1.000, Monotonicity 1.0 implied by sequential IDs) provides a scrape-order sequence, but this is an artifact of data collection, not a semantic event ordering of the bouts themselves. Each row describes a complete boxing match with its outcome and both fighters' attributes at that point in their careers — the f_boxer_won progression (0→33) shows career state snapshots, not match-level events. The rounds column encodes the match result but no intra-match event sequence. With each bout uniquely identified and no natural time axis ordering the entity's actions, this is dimension. The weak event reading comes from the sequential scrape order, but that orders data collection, not boxing events." } ```