Real-Time Entity and Network Generation Action Set

This section contains PROC CAS code.

Note: Input data must be accessible in your CAS session, either as a CAS table or as a transient-scope table. A CAS table has a two-level name: the first level is your CAS engine libref, and the second level is the table name. You refer to this table in the CAS procedure by specifying only the second level. For more information about two-level names, see Chapter 2, Shared Concepts (SAS Viya: Machine Learning Procedures). A transient-scope table is called directly from the action and exists in memory for the duration of the action. For more information about accessing data, see SAS Viya: System Programming Guide. For more information about PROC CAS and programming in CASL, see SAS Cloud Analytic Services: CASL Programmer’s Guide and SAS Cloud Analytic Services: CASL Reference.

This example illustrates how to use the queryCompounds action to generate entities and networks for specific documents. The example assumes that you have already run Example 32.2.

data mycas.query_compounds;
   infile datalines dsd;
   length compound_value $32. compound_type $32.;
   input compound_value $ compound_type $;
   datalines;
JAMES~MORRIS~11769, namedob
;

proc cas;
   action rteng.queryCompounds /                                     /* 1 */
      compounds = {
         {compoundValue="JAMES~MORRIS~11769" compoundType="namedob"} /* 2 */
      }
   /* compounds = {{name="query_compounds"}}                            2 */
      output = {name="query_compounds_out" replace=true}             /* 3 */
      outputCompoundValue = true                                     /* 4 */
      outputSubEntityId = true                                       /* 5 */
      softDeleteEntities = {                                         /* 6 */
         {
            entityType="address"                                     /* 7 */
            temporalSplitting=true
            hasAttribute={{attribute="role" value="business"}}
         }
      }
      softDeleteLinks = {                                            /* 8 */
         {
            documentType="claim"                                     /* 9 */
            entityType="individual"
            hasAttribute={{attribute="role" value="supplier"}}
         }
         {
            documentType="claim"
            entityType="address"
            hasAttribute={{attribute="role" value="supplier"}}
         }
      }
      ;
   run;
quit;

Specific lines of the code (as numbered in the comments) are described as follows:

Output 32.5.1 is the output table of the queryCompounds action. It contains a row for each compound that is formed on each network for the specific documents being queried. The compounds are grouped into entities; the grouping is denoted by the _entity_id_ variable. The links between entities and documents are grouped into networks; the grouping is denoted by the _network_id_ variable.