PHPMem v2.0.1
Version
1.6.45
Uptime
18 days 9 hours 7 minutes 19 seconds
Memory
Total
512MB
Used
12,33MB (2.41%)
Free
499,67MB
Keys
Current
13 424
Total (since start)
40 994
Evictions
0
Reclaimed
762
Expired Unfetched
0
Evicted Unfetched
0
Connections
Current
3 / 1 024 max
Total
245 664
Rejected
0
llm:6763f093415f1d17297dbf4af57b095abab0525005e3b5579566420f2fbd5a80
Edit
{
"table_name": "startup_funding",
"table_type_tags": [
{
"tag": "event",
"confidence": 0.6
},
{
"tag": "dimension",
"confidence": 0.3
},
{
"tag": "path",
"confidence": 0.22
}
],
"primary_type": "event",
"insufficient_evidence": false,
"entity": {
"columns": [
"Startup Name"
],
"unique_per_row": false
},
"time_axis": {
"columns": [
"Date dd/mm/yyyy"
],
"kind": "event_time"
},
"reasoning": "Each row is a funding deal that happened to a startup on a given date. Startup Name repeats (RPUV 1.24, Uniqueness 0.808, Ola Cabs and Swiggy with 8 rows each) and Date dd/mm/yyyy is a full event timestamp (1,035 distinct values, stored as text). Sr No (Uniqueness 1.000) is only a row counter, not a catalog ID. Replaying the rows would not reconstruct a clean entity state: Amount in USD is 'N/A' in 959 rows and is messy text, so the rows read as bare occurrences, which points to event. The dimension and path readings are weaker alternatives. Dimension applies because Sr No is unique per row and each record carries descriptive attributes. Path applies because funding stage and cumulative funding could loosely be replayed."
}