Process Element Annotation for MitigatingProcess Semantic Collapse: A Constraint-AwareDecomposition–Recomposition Approach
This paper introduces the constraint-aware Decomposition–Recomposition Process Element Annotation (DR-PEA) method to mitigate Process Semantic Collapse in large language models by transforming unstructured process text into standardized structured data through a three-stage pipeline of semantic decomposition, process recomposition, and constraint mapping, achieving superior performance over existing baselines.
Original paper licensed under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
The Problem: When AI "Flattens" a Recipe
Imagine you ask a very smart but slightly literal robot to turn a complex cooking recipe into a simple list of steps.
The recipe says: "If the sauce is too salty, add sugar. If it's too sweet, add salt. While the sauce simmers, chop the onions. Once the onions are ready, add them to the pot."
A standard AI (Large Language Model) might try to summarize this and say:
"Add sugar if salty, add salt if sweet, simmer the sauce, chop onions, and add onions."
What went wrong?
The AI missed the structure. It turned a branching decision tree (If/Then) and parallel tasks (doing two things at once) into a single, straight line. In the paper, the authors call this "Process Semantic Collapse."
It's like taking a 3D sculpture of a tree and squashing it flat onto a piece of paper. You can still see the leaves and branches, but the tree has lost its shape, its depth, and its ability to actually grow.
The paper identifies three ways this "squashing" happens:
- Boundary Collapse: Merging two separate steps into one giant, confusing step (e.g., "Chop onions and add them" becomes one blob).
- Gateway Collapse: Turning a "If/Or" choice into a straight "Do A then Do B" line.
- Relation Collapse: Mixing up who does what (e.g., saying the pot chopped the onions instead of the chef).
The Solution: The "Architect's Blueprint" Approach (DR-PEA)
Instead of asking the AI to write the whole final story in one go (which leads to the "squashing" problem), the authors propose a method called DR-PEA (Decomposition–Recomposition Process Element Annotation).
Think of this not as asking the AI to write a novel, but asking it to act as a construction crew building a house. You don't tell the crew, "Build a house!" and hope they get the blueprints right. Instead, you break the job down:
Phase 1: The Scavenger Hunt (Semantic Decomposition)
First, the system scans the text to find specific "bricks" (process elements).
- It looks for Actors (who is doing it?).
- It looks for Activities (what are they doing?).
- It looks for Conditions (when does this happen?).
- The Trick: Instead of letting the AI guess the whole sentence, it forces the AI to point to exact words in the text, like highlighting them with a marker. This prevents the AI from merging two different steps into one long, messy highlight.
Phase 2: The Assembly Line (Process Recomposition)
Now that the bricks are found, the system tries to snap them together.
- It asks: "Does this 'Actor' connect to this 'Activity'?"
- It checks: "Is this a 'If/Then' branch or just a straight line?"
- The Trick: The AI is only allowed to connect the specific bricks it found earlier. It can't invent new connections or skip steps. It's like a game of Connect-the-Dots where the dots are already numbered, and the AI just has to draw the lines between the right numbers.
Phase 3: The Safety Inspector (Constraint Mapping)
This is the most important part. Before the final blueprint is approved, a strict "Safety Inspector" checks the work against a rulebook.
- Rule 1 (The Dictionary Check): If the system thinks "The System" is an actor, does it contain a word from our "People/Role" dictionary? If not, delete it.
- Rule 2 (The Length Check): If a step description is too long (like a whole paragraph), it's probably a mistake. Cut it down.
- Rule 3 (The Grammar Check): If the text says "The employee," make sure the system includes the word "The" in the label, because that's how the real-world experts wrote it.
Why This Works Better
The paper tested this method against standard AI prompts.
- Standard AI: Tries to be fluent and fast, but often "squashes" the structure (Semantic Collapse).
- DR-PEA: Is slower and more rigid, but it acts like a quality control inspector. It forces the AI to slow down, check its work against hard rules, and rebuild the structure piece by piece.
The Results:
On a test set of business process texts, the DR-PEA method significantly reduced these "squashing" errors.
- It correctly identified the "bricks" (mentions) much better than before.
- It correctly connected the "bricks" (relations) much more accurately.
- It created a clean, structured map (JSONL format) that computers can actually use to understand business processes.
The Bottom Line
The paper argues that you can't just ask a smart AI to "understand" a complex process and write it down. The AI's natural tendency is to smooth things over and make them look like a simple story.
To fix this, you have to decompose the task (break it into tiny, verifiable pieces), recompose it (put the pieces back together), and constrain it (force it to follow strict rules). This turns a "creative writer" AI into a precise "structural engineer," ensuring that the final output is a working blueprint, not just a flattened picture.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.