Upgraded to 2025, What is this netflix sentiment analyzer in the coldfusion-out.log

I have ColdFusion 2025 on Windows. Though I don't see those INFO lines in coldfusion-out.log, I can confirm that my installation has the file C:\ColdFusion2025\cfusion\jetty\work\jetty-127_0_0_1-8997-solr_war-_solr-any-\webapp\WEB-INF\lib\sentiment-analysis-parser-0.1.jar

It suggests that ColdFusion 2025 is making use of https://github.com/USCDataScience/SentimentAnalysisParser 

Must be some Adobe spyware! Just kidding (though some would assert that must be it)!

First, I can say that I've never seen that in thousands of coldfusion-out.log files I've seen, and hundreds for cf2025. As such, this seems very unique to you...and thus is likely environmental. I can also confirm that I have that same sentiment-analysis-parser-0.1.jar file within my CF2025 jetty\work folder at about the same path, since I'd implemented the Solr feature of CF. But again I am seeing no such LOG entry as you report.

Let's note about that the info message that the thread-id indicates it arose based on a request coming into CF--specifically coming on your port 8024, which is the AJP port. That means the request came into CF by way of your web server, such as iis or apache (as opposed to the port 8500 which is the built-in web server used for the CF admin).

Even so, and especially since the request seems recurrent, you might want to check if perhaps you have a cf admin scheduled task running at that frequency (it could call a URL which ends up on your server, coming through your web server)? Please do check your admin scheduled tasks page. 

And I realize you you say you "just" installed this cf instance, in which case you might be tempted to say you "didn't add any tasks". Even so, you technically say you "upgraded" cf, which implies you had a prior cf version on the same machine. Is that right?  

If so, during the first launch of the cf admin you (or someone) would have been asked if you wanted to migrate in the cf admin settings from the previous version. If you did that, perhaps something got migrated you're not expecting. Note there is a migration log in the cfusion/logs folder if you did that, showing what was migrated. It might be worth a look.

Finally, since the requests are coming in via your web server, check your IIS or Apache logs for the times shown. That will show the URL as well as the originating IP address (and user agent). Let us know what you find.