Absolutely not. A Dune type would not be “perfectly reasonable”. It’s a movie that related to a book (and vice versa), a soundtrack that’s related to a movie, etc. Those are different types. Cramming all that into one type is not reasonable at all. However, they could be in multiple collections: a book collection, a movie collection, and, yes, a Dune collection. But only the first two collections are referring to their respective type.
Funny example. I have something very similar in LogSeq and it doesn’t require AI at all. It just parses the block I created and links all the keywords. The name of the person refers to that persons page (which can also have aliases), the word “movie” would link to the movie page. The only real thing I have to do is the “I want to watch it”, which would require me to add TODO to the beginning of the block to make it a task on my todo list. I think I can manage that pretty well without AI.
And actually, I think you can do pretty much the same with Anytype. Put an @ in front of the persons name and it’s linked, right? However, you can’t quickly assign a type on creation this way. You would always get the default type for the space and then need to manually change it to a task for instance. Or you can create a blank task and then you would immediately be taken to the page of the task to fill in the details, which breaks workflow. So it would be better if you could create a link to a new object of an arbitrary type and just needed to input the title, so you could keep writing what you’re writing and fill in any details later. Something like @task[Call Ghostbusters].
(I’m intentionally ignoring “next month” since that is not helpful information at all. You would have to have a specific date, when the movie is released and/or when you want to watch it.)