@AkkuH  

Why are you using 'Save As'?  Are you trying to save it into a higher ruleset? 

Please see the functionality of Decision Data Rules: 

Completing the Decision Data rule form

Please could you have a look at this previous forum question Alternate source for spellcheck dictionary and Entity Extraction using a dictionary?

See the official documentation:

Creating Decision Data rules that contain scripts for entity extraction

 Best practices for pattern extraction in text analytics

Ruta requirements and considerations for Pega applications

Consider the following points when creating Ruta-based entity types in Pega Platform:

• To store annotation results, mark them in the Ruta script. You can use the VarA, VarB, VarC, VarD, and VarE variables to store intermediate annotation results. Pega Platform stores the final annotation results in the EntityType annotation, the name of which is equal to the Entity type name property
• Always clear the declared variables, such as VarA, at the end of your script, so that they do not interfere with the execution of the next script.

• Pega Platform does not support WORDLIST and WORDTABLE annotations. Starting from Pega Platform 8.3, you can define wordlists as keywords and refer to them in the Ruta script.

• Starting from Pega Platform 8.3, you can reference other entity types through the Ruta script by using the following command: EntityType{FEATURE("entityType", "<EntityTypeNameInLowerCase>")}. For an example of a use case, see Improve the management of text extraction models through entity types.Reference entity types in lowercase, irrespective of the case in which you defined them.
• In Pega Platform, Ruta script can detect only a single entity type.

For more information, see Creating entity models.

Can you confirm that this question is a duplicate of your other forum question posted 2 days ago ?   RUTA scripts to extract values from table?