How to use the Argument Map Generator.
Argument maps should separate premises, conclusions and objections. Represent the author's reasoning without silently repairing missing support.
Make the workflow fit your task.
Identify the main conclusion and the premises offered in support, retaining the author's wording where necessary. Show intermediate conclusions, objections and unstated assumptions as separate nodes. Do not strengthen the argument by silently supplying missing evidence.
- What you provide
- Argumentative article or debate text.
- What you get
- Claims, premises, evidence and objections.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Text argues a process should change because errors occur during manual re-entry.
Completed example
Map the error observation as a premise, process change as the conclusion and missing evidence about alternatives as an open issue.
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 implied assumption be represented as a quoted premise?
No. Label it as an inferred assumption and explain how it connects the stated reasons to the conclusion.
Why does the map contain an unsupported jump between two claims?
The source may omit a necessary link. Keep that gap visible rather than inventing a supporting premise.
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 ↑