The approach that occurs to me would be to put your keyword tests into a subroutine and use the each function to test the sentences in a way that makes the index / sentence number easily accessible.
while (($key, $value) = each @sentence) { if (has_one_or_more_keywords($value)) print "$key: $value\n"; }
I second the suggestion to consider an HTML parsing module. You may also want to consider replacing your sentence and word splits with a more sophisticated grammar for parsing sentences and words using a module like Parse::RecDescent. For example, the period character is not a sentence terminator when used in an ellipsis, as a decimal point in a number, etc.

In reply to Re: Searching through a document and reporting results. by mvaline
in thread Searching through a document and reporting results. by Tails

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.