What you are describing is not supported by the javadoc generation tool.
And I think that there is a good reason for this too:
If your method in the subclass is merely an implementation of an abstract method, then I think it would be correct to leave the abstract class’ name in there.
On the flip side, if your method in the subclass is not just a simple implementation, and does something more that is noteworthy (enough to be mentioned in the javadoc), then you should write a new javadoc on the method in the subclass, instead of invoking inheritDoc.