CHICAGO — Jake Bennett allowed four hits in seven innings, Tsung-Che Cheng had his first multi-RBI game and the Boston Red Sox beat the Chicago White Sox 5-0 on Wednesday night for their fifth straight victory.
Boston has won 10 of 12 and 13 of its last 18.
Bennett (4-3) has allowed more than two runs just twice in eight starts. He struck out four and walked one.
Cheng had an RBI single in the third to give the Red Sox a 1-0 lead, and Ceddanne Rafaela drove in Cheng two batters later.
Anthony Seigler came across on a wild pitch from Davis Martin (9-4), but Seigler left the game after a collision with catcher Kyle Teel at the plate.
Willson Contreras, who committed to the Home Run Derby before the game, also left the game with an injury. He fouled a ball off of his left foot, initially remained in, but was removed with one out in the bottom of the third.
Carlos Narváez hit an RBI single of his own and Cheng added his second RBI of the night in the fourth.
For the White Sox, Luisangel Acuña went 2 for 2.
Up next
Left-hander Patrick Sandoval was set to make his Red Sox debut against White Sox left-hander Anthony Kay (6-3, 4.39 ERA) on Thursday in the series finale. Sandoval was activated Monday after a two-year recovery from Tommy John surgery.
Comments are not available on this story. Read more about why we allow commenting on some stories and not on others.
We believe it's important to offer commenting on certain stories as a benefit to our readers. At its best, our comments sections can be a productive platform for readers to engage with our journalism, offer thoughts on coverage and issues, and drive conversation in a respectful, solutions-based way. It's a form of open discourse that can be useful to our community, public officials, journalists and others.
We do not enable comments on everything — exceptions include most crime stories, and coverage involving personal tragedy or sensitive issues that invite personal attacks instead of thoughtful discussion.
You can read more here about our commenting policy and terms of use. More information is also found on our FAQs.
Show less