How to use the Press Release Fact Sheet Extractor.
A press-release fact sheet should attribute claims to the issuing organization. An announcement is not independent verification that a promised outcome occurred.
Make the workflow fit your task.
Extract issuer, announcement date, named people, planned milestones and stated figures. Attribute claims to the issuing organization and separate completed events from future commitments. Keep source references so the fact sheet can be checked when plans change.
- What you provide
- Visible press release.
- What you get
- Attributed announcements, dates, figures and stated claims.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Fictional Example Co release dated 1 September 2026: "We plan to launch our offline notes feature in October 2026." No launch confirmation supplied.
Completed example
Issuer: Example Co. Announcement date: 1 September 2026. Announced feature: offline notes. Planned timing: October 2026. Status: company-stated plan, not a confirmed completed launch. Follow-up needed: check an actual release record before reporting availability.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should an announced launch date be written as a completed launch?
No. Preserve the announcement's future status until independent or subsequent evidence confirms the event occurred.
Why does the fact sheet sound more certain than the release?
Words such as plans, expects or aims may have been removed. Restore them where they qualify a claim.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑