You will note that the data doesn't have a unique id. Title certainly isn't unique, if you consider how many movies there have been called Batman or Treasure Island.
Now I may encounter data about this movie from another source that covers different facets , for example it's box office takings or movie reviews.
So it's a classic semantic web application. I want to amalgamate disparate data about the same fact in one entity. As I said I have a transformation that does this but it doesn't scale very well because I have to search the entire movie base to find the best match. To overcome this I have to adopt a mapReduce-ish approach to solve the problem.
The thinking is a graphical representation would eliminate that problem because a graph gives me a persistent data structure already indexed for retrieval via several different axes, whereas indexes constructed in the XSLT transformation for the same purpose are ephemeral and would need to be reconstructed every time you ran the transformation.