Stabbing near University Way prompts suspect description and tip line
AI-generated · every claim is source-linkedOn July 8, 2026, the UW Alert Blog posted that Seattle police were investigating a stabbing near N 47th Street in the alleyway between University Way and Brooklyn Avenue NE, with a suspect description and a follow-up tip-line update under SPD case 198943.
- Alerts
- 2
- Response
- —
- Killed
- —
- Injured
- —
Alert Sequence
2 messages in sequence · 2 verified verbatim
Confirmed wording is transcribed character-for-character from a primary source. Use Verify this quote under each message to open that source in a new tab and compare the text yourself.
How the first alert is built
To check this alert, Claude (an AI) read it in full 25 separate times, independently. Each read decided whether the message answers each of the six questions and gave a short reason. A final reviewer then weighed all 25 and wrote the plain-English verdict you see when you open a row. The score (for example 22/25) is how many reads agreed; the 25 individual reads are tucked underneath if you want to check them.
7:12 p.m.: Seattle police are investigating a report of a stabbing that occurred near N 47th Street in the alleyway between University Way and Brooklyn Avenue NE at about 7 p.m. The suspect was described as a man with dirty blond hair in his 30s wearing blue shorts and no shirt. The suspect, who had a limp, may have left the area headed north on a bike.
Sourcepresent25/25
Final assessment
All 25 reads agree (1): Seattle police "are investigating" the stabbing report.
Who is sending the alert and who is responding. People act faster on a message from a clearly identifiable, credible sender, such as a named department, the police, or a branded alert system, than on an anonymous notice. A branded signature counts.
See all 25 individual reads
- present: Seattle police "are investigating" the stabbing report.
- present: Seattle police are identified as the investigators of the report.
- present: Names Seattle police as the investigating agency source.
- present: Points to "Seattle police" as the agency on the case.
- present: Seattle police are named as the investigating agency source.
- present: The message names its source because Seattle police are listed as the investigating agency.
- present: Names Seattle police as the investigating agency source.
- present: Seattle police are named as the investigating agency.
- present: Since Seattle police are cited as the investigating agency.
- present: Identifies Seattle police as the investigating source.
- present: Seattle police are presented as the agency running the investigation.
- present: Identifies "Seattle police" as the unit on the case.
- present: Seattle police named as the unit on the stabbing report.
- present: Identifies Seattle police as the authority handling the stabbing report.
- present: Seattle police are named as the agency on the case.
- present: Seattle police on the stabbing case.
- present: Identifies Seattle police as the agency looking into the matter.
- present: Seattle police are the ones said to be looking into the stabbing.
- present: Checklist: Seattle police are identified as the authority handling the report.
- present: Lead identifies Seattle police as the agency on the case.
- present: Seattle police are named as the agency undertaking the investigation.
- present: Seattle police are identified as the agency handling the report.
- present: Seattle police are the stated lead on this stabbing report.
- present: Seattle police are the agency handling the stabbing report.
- present: Seattle police still own the case wording after a skeptical re-read.
Hazardpresent25/25
Final assessment
All 25 reads agree (1): Hazard named is a "stabbing that occurred" nearby.
What the threat actually is. A complete warning names the specific danger, such as a shooter, a fire, a tornado, or a gas leak, rather than a vague emergency, because people decide what to do based on what they are facing.
See all 25 individual reads
- present: Hazard named is a "stabbing that occurred" nearby.
- present: A stabbing is the incident type under review.
- present: Identifies a stabbing as the specific hazard.
- present: Calls out a "stabbing" as the specific crime hazard.
- present: Stabbing is named as the specific reported hazard or crime.
- present: The message labels the crime because it reports a stabbing.
- present: Specifies stabbing as the concrete hazard.
- present: Stabbing is named as the specific hazard.
- present: Because a stabbing is identified as the specific hazard.
- present: Names a stabbing as the specific hazard.
- present: A stabbing is named as the specific hazard.
- present: Names a "stabbing" as the hazard under review.
- present: Hazard is a stabbing near N 47th.
- present: Specifies a stabbing as the hazard type.
- present: Reports a stabbing as what took place.
- present: Stabbing. Event named.
- present: States a stabbing as the reported offense.
- present: They call it a stabbing, so the hazard type is on the page.
- present: Checklist: hazard is a stabbing.
- present: Incident type is a stabbing.
- present: The hazard is identified as a stabbing.
- present: A stabbing is named as the specific crime under review.
- present: Stabbing is named as the incident type.
- present: Hazard named is a stabbing near the stated streets.
- present: Stabbing remains the named event; no other threat word is hiding in the text.
Locationpresent25/25
Final assessment
All 25 reads agree (1): Site is the alley near N 47th between University Way and Brooklyn Avenue NE.
Where the threat is. Saying whether danger is in a specific building, a part of campus, or area-wide lets people judge their own proximity and choose a safe direction. Without a where, a warning is hard to act on precisely.
See all 25 individual reads
- present: Site is the alley near N 47th between University Way and Brooklyn Avenue NE.
- present: The event is located near N 47th Street in the alley between University Way and Brooklyn Avenue NE.
- present: Specifies N 47th Street alleyway between University Way and Brooklyn Avenue NE.
- present: Maps it to the "alleyway between University Way and Brooklyn Avenue NE" near "N 47th Street."
- present: Near N 47th Street in the alley between University Way and Brooklyn Avenue NE.
- present: The message maps the scene because it cites the alley near N 47th between University Way and Brooklyn Avenue NE.
- present: Details N 47th Street alley between University Way and Brooklyn Avenue NE.
- present: Alleyway near N 47th Street between University Way and Brooklyn Avenue NE is specified.
- present: Although dense, it maps the alley near N 47th between University Way and Brooklyn Avenue NE.
- present: Specifies N 47th Street alleyway between University Way and Brooklyn Avenue NE.
- present: The site is fixed to an alley near N 47th between University Way and Brooklyn Avenue NE.
- present: Maps it "near N 47th Street in the alleyway between University Way and Brooklyn Avenue NE".
- present: Alley fix: N 47th between University Way and Brooklyn Ave NE.
- present: Gives the alley near N 47th Street between University Way and Brooklyn Avenue NE.
- present: Describes the alley near N 47th between University Way and Brooklyn Avenue NE.
- present: Alley off N 47th, University Way to Brooklyn Ave NE.
- present: Specifies the alley near N 47th Street between University Way and Brooklyn Avenue NE.
- present: Location is the alley near N 47th between University Way and Brooklyn Avenue NE.
- present: Checklist: alley near N 47th between University Way and Brooklyn Avenue NE.
- present: Where: alley near N 47th between University Way and Brooklyn Avenue NE.
- present: The event is placed in the alley near N 47th Street between University Way and Brooklyn Avenue NE.
- present: The site is an alleyway near N 47th between University Way and Brooklyn Avenue NE.
- present: Alley near N 47th between University Way and Brooklyn Avenue NE is specific.
- present: Site is the alley by N 47th Street between University Way and Brooklyn Avenue NE.
- present: Alley near N 47th between University Way and Brooklyn Avenue NE is still the site.
Guidanceabsent0/25
Final assessment
All 25 reads agree (0): Suspect clothing and limp notes lack any protective order for readers.
The protective action to take. A clear, specific instruction, such as shelter in place, evacuate, avoid the area, or run-hide-fight, drives faster and more correct protective behavior than describing the threat alone.
See all 25 individual reads
- absent: Suspect clothing and limp notes lack any protective order for readers.
- absent: No guidance tells readers how to protect themselves or what action to take.
- absent: Offers no protective action for recipients, only investigation and suspect details.
- absent: Gives suspect details only; no action step for the reader.
- absent: No protective action is directed to the recipient, only investigation details.
- absent: The message withholds guidance because it never tells recipients any protective action to take.
- absent: Offers no protective action directed to the message recipient.
- absent: No protective action is directed to the recipient.
- absent: Since no protective action is aimed at recipients, only suspect details appear.
- absent: Gives no protective action for the recipient to take.
- absent: No protective action for recipients is being offered.
- absent: Offers no recipient instruction such as avoid, shelter, or call.
- absent: No action line aimed at the reader.
- absent: Provides no protective instruction aimed at the message recipient.
- absent: Offers no protective step for readers, only suspect details.
- absent: No action order for the public.
- absent: Provides no action recipients should take for their own protection.
- absent: You get a suspect sketch but nobody tells you what to do to stay safe.
- absent: Checklist: no protective action aimed at the recipient.
- absent: Suspect description only; no avoid, shelter, or other action for readers.
- absent: Suspect description and travel notes supply no protective instruction to recipients.
- absent: Only suspect description is provided; no protective action is directed at recipients.
- absent: Suspect clothing and limp notes only; no protective action for the public.
- absent: Suspect look and bike path are given with no protective order for readers.
- absent: Second look still finds zero ask of the public, only suspect clothes and path.
Timepresent25/25
Final assessment
All 25 reads agree (1): Event is pegged at "7:12 p.m." with the act "at about 7 p.m."
When the message applies. A timestamp, the word now or immediately, or a phrase like until further notice tells the reader whether the danger is current and how quickly to act.
See all 25 individual reads
- present: Event is pegged at "7:12 p.m." with the act "at about 7 p.m."
- present: Both a 7:12 p.m. release time and an approximate 7 p.m. occurrence are given.
- present: Includes 7:12 p.m. alert time and about 7 p.m. for the incident.
- present: Uses alert time "7:12 p.m." and incident time "about 7 p.m."
- present: Gives 7:12 p.m. and that the stabbing occurred at about 7 p.m.
- present: The message notes timing because it gives 7:12 p.m. for the alert and about 7 p.m. for the event.
- present: Includes 7:12 p.m. alert time and about 7 p.m. occurrence time.
- present: Timestamp 7:12 p.m. and incident time about 7 p.m. are given.
- present: Because it includes 7:12 p.m. and about 7 p.m. for when it happened.
- present: Includes 7:12 p.m. alert time and about 7 p.m. incident time.
- present: A 7:12 p.m. alert time and about 7 p.m. incident time are included.
- present: Gives alert time "7:12 p.m." and occurrence "about 7 p.m.".
- present: Alert clock 7:12 p.m.; incident about 7 p.m.
- present: States 7:12 p.m. for the alert and about 7 p.m. for the incident.
- present: Includes 7:12 p.m. for the alert and about 7 p.m. for the stabbing.
- present: Alert 7:12 p.m. Act about 7 p.m.
- present: Gives 7:12 p.m. for the alert and about 7 p.m. for the incident.
- present: Alert time is 7:12 p.m. and the stabbing is pegged around 7 p.m.
- present: Checklist: 7:12 p.m. alert time plus about 7 p.m. event time.
- present: Alert time 7:12 p.m. with event around 7 p.m.
- present: Both a 7:12 p.m. alert time and an about 7 p.m. occurrence time appear.
- present: Both a 7:12 p.m. alert time and an about 7 p.m. occurrence time appear.
- present: Gives 7:12 p.m. release time and about 7 p.m. for when it happened.
- present: Gives 7:12 p.m. for the notice and about 7 p.m. for the stabbing.
- present: 7:12 p.m. and about 7 p.m. both stay as clear time anchors.
Impactabsent0/25
Final assessment
All 25 reads agree (0): Description of the man on a bike never states injury severity or wider harm.
What the hazard could do to the people in its path. Beyond naming the threat, a complete warning conveys its potential consequences or severity, such as that a tornado can level buildings or that a leak could be explosive, so recipients grasp how much danger they are in. Research on warning message content finds that a concrete impact statement helps people personalize their risk and act sooner.
See all 25 individual reads
- absent: Description of the man on a bike never states injury severity or wider harm.
- absent: Suspect looks and escape path replace any statement of victim harm severity.
- absent: Adds no consequence or severity beyond naming the stabbing itself.
- absent: Describes hair, clothes, and limp, not harm or severity to victims.
- absent: No consequence or severity is stated beyond naming the stabbing.
- absent: The message skips impact detail because suspect looks and travel path do not state harm or severity.
- absent: Suspect description alone does not state severity beyond the stabbing name.
- absent: No consequence or severity is stated beyond naming the stabbing.
- absent: Although a stabbing is reported, no severity or consequence language is added.
- absent: Suspect details do not state consequence or severity beyond the stabbing.
- absent: Suspect description is given without stating consequence or severity.
- absent: Suspect looks and limp detail convey no stated consequence or severity.
- absent: Suspect look and limp are ID notes, not impact.
- absent: Suspect description alone does not convey outcome severity.
- absent: Hair, clothes, limp, and bike clues do not state impact or how bad it was.
- absent: Suspect looks and limp, not impact.
- absent: Suspect appearance and flight path do not establish impact or seriousness.
- absent: Hair, clothes, and the limp do not add severity or what the attack might mean for others.
- absent: Checklist: suspect description only; no consequence or severity line.
- absent: No consequence or seriousness beyond the stabbing label.
- absent: Nothing in the text establishes injury severity or broader consequence.
- absent: No severity or consequence wording is present beyond naming the stabbing.
- absent: No stated injury outcome or broader harm beyond the stabbing label.
- absent: No severity or outcome is stated past naming the stabbing.
- absent: Hair, shorts, limp, and bike notes never grade how serious the attack was.
Systematic AI judgments with visible reasoning, not human-validated codings.
About this analysisBackground
Key Findings
Sources
Every claim on this page is meant to be checkable. Open the links below (and the Verify this quote control under each confirmed alert) to read the original university, news, or archive page yourself. Hostnames are shown so you can see where you are going; archived copies survive when live pages move or disappear. See also our methodology.
- Official
Campus Alert Archive. "University of Washington: Stabbing near University Way prompts suspect description and tip line." Incident of July 8, 2026. Added July 2026. https://campusalertarchive.com/case/university-of-washington-university-district-stabbing-2026-07-08/
Alert text quoted on this page remains the work of the issuing institution; the archive is a secondary source.