Another candidate (besides a happily-misappropriated Component) for a relatable parsing container is the Artifact (a Classifier):

PROS:

1. can be packaged
2. can carry Dependency relationships to other "relatable" NamedElements
3. little note icon suggests a documents (and thus is a good container for parsed text)
4. well distinguished from software engineering elements like Class or Component
5. can contain/own other elements (like other Comments or Artifacts)
   • can be nested to build nice logical trees of parsed text in your analysis model

CONS:

1. One can't use HTML text style:
   • I recommend setting Header in Bold option off and word wrap on
2. In MagicDraw UML one can't create an Artifact under a Component (so one can't easily insert an Artifact into a wrapper Component)
   1. create the Artifact under the nearest Model/Package IN THE BROWSER then
   2. move it IN THE BROWSER into the desired owrning wrapper Component
      (since you are using UML Parsing Analysis it almost certainly want to do that), then
   3. use create symbol to show the parsing Artifact in the diagram:
   • • is a WORKAROUND (a bit tedious, however the results can be rewarding):
3. In MagicDraw UML Artifact is only available on diagram menus of certain diagram types (and especially not in SysML diagrams)

Despite these subtleties, if you want powerful text analysis modelling results, this is one good strategy

Image: