"update" Rolesets

update

update.01 - make more modern, bring up to date

ARGs 2 and 3 added based on evidence in THYME-AMR. Compare/contrast CT-scan example with: the website is updating, where website is ARG1; the website is becoming modernized/updated. In updated CT-scan, the scan itself is the thing constituting the update; it's the newest version. For these cases, ARG1 is unlikely to be explicit; it seems it would only be filled by a generic reference to the type of scan (something like, 'In terms of CT scans, we'll get an updated one'?? Again, unlikely to occur).
UPDATE-V NOTES: No Vncls. (from update.01-v)
UPDATE-N NOTES: Based on Bolt data. Comparison to update.01-v. Consitant with VN class tell-37.2. No FN classes. Framed by Katie. (from update.01-n)

Aliases:

update (v.)
update (n.)

Roles:

ARG0-PAG: updater
ARG1-PPT: thing being modernized or updated
ARG2-GOL: most recent (updated) version
ARG3-SRC: prior (outdated) versions

update-v: transitive

Batch processing is the high - volume , single - job data processing that most mainframes typically chug through at night , such as .

ARG2

An updated CT scan of the abdomen and pelvis was obtained .

          (c / ct-01
            :ARG1 (a / and
              :op1 (a2 / anatomical-site :name (n / name :op1 "abdomen"))
              :op2 (a3 / anatomical-site :name (n2 / name :op1 "pelvis")))
            :ARG2-of (u / update-01))

update.02 - tell someone news as it comes

UPDATE-V NOTES: Added by Julia based on BOLT. Member of VNcls tell-37.2. (from update.02-v)

Aliases:

update (v.)
update (n.)

Roles:

ARG0-PAG: teller
ARG1-GOL: hearer
ARG2-PPT: news

update-v: args 1, 2

I will keep .

update-n: arg1

The transport crew received the .