You should not use <title> here. The title should be used to describe the image, if that makes sense for someone that can't see the image. In this case, it is obvious that the icon itself doesn't need any description. But the message it brings to people who can see it, is what you should focus on. When the image isn't visible (for either a human or ...
If there is no value in describing the image then there is no value in using title. You do not need to title (or alt) every image just because it's there. (Note that alt is a required attribute so alt="" would be appropriate.)
Use such things to describe an image to a person who is unable to view the image for any reason. Whether sight impaired or the image ...
The <title> should be used as if it were an alt tag, describing the item for screen reader users as if it was just a .png or similar.
I answered a similar question on Stack Overflow explaining how to think of the <title> and <description> elements (among other things, first couple of paragraphs are most relevant to you.)
(1) Ellipses + read more
This will create confusion as the entire is ideally clickable. Also, read more usually shows the full content in the current view (according to common patterns).
(2) Ellipsis + tooltip
I will not advise the usage of tooltip since once users already know what it does it will become redundant having it on each column.
(3) Just make ...
Rather old question.
More info on what's the nature of data would help.
Sounds like you have a lot of categorized properties for every topic. Like properties of a product: weight, size, dimension.
Therefore, althow it sounds obvious, you should rotate your table 90 deg to make topics be columns and properties - rows.
If there is no need to see all ...