Number fields with "time" in name incorrectly parsed as timestamps

[AI091]

Bug description

Number fields interpreted as dates. I have an event where it contains an entry called parsing_time_in_seconds. It's a number as shown in the screenshot. However it doesn't appear in trends selection in number choices and upon using hogql queries on it it is converted to a timestamp, the only way I found around it is by using JSONExtractFloat method to force parse it as a number, but that means I can't use it nicely in dashboards.
I am assuming having the word time in the property somehow makes it auto-parse to time_stamp, is this the intended behavior?

link on Posthog Cloud for the query:https://eu.posthog.com/project/32299/insights/V05z1kHc/

How to reproduce

1. Create event with numeric property containing word time
2. See that property is auto intepreted as timestamp and is unsable in trends as a number.

Debug info

- [x] PostHog Cloud, Debug information: Session: https://us.posthog.com/project/sTMFPsFhdP1Ssg/replay/0195375c-6e4a-7a51-874b-fb216c51cb13?t=6368
Admin: http://go/adminOrgEU/0191e5ad-b2a6-0000-986b-d89fef3ca53f (project ID 32300)
Sentry: http://go/sentryEU/32300(https://posthog.com/blog/sunsetting-helm-support-posthog)),

[ordehi]

Thanks for the report! You can change the property's data type to numeric under data management and that should fix the query.

I tested this and it's indeed treating anything with "time" in the name as a datetime, at least for insights purposes, even though in the event it's treated as a number: