NEW YORK
The road to the winner’s circle in the Belmont Stakes ran through the Kentucky Derby, even if the Derby and Preakness winners skipped the final leg of the Triple Crown.
Tapwrit overtook favored Irish War Cry in the stretch to win by two lengths on Saturday, giving trainer Todd Pletcher his third career victory in the Belmont. He won in 2007 with filly Rags to Riches and in 2013 with Palace Malice.
The first four finishers all followed a well-worn path: run in the Derby, skip the Preakness and come back fresh for the Belmont. Five of the last nine Belmont winners did just that.
Tapwrit finished sixth in the 20-horse Derby after encountering traffic in what Pletcher described as “a sneaky good” race.
“We felt like with the five weeks in between, and with the way this horse had trained, that he had a legitimate chance,” said Pletcher, who is based at Belmont Park. “I think that’s always an advantage.”
Irish War Cry was 10th after pressing the early pace in the May 6 race.
Patch took third in the Belmont after being 14th in the Derby. Gormley, ninth in the Derby, finished fourth Saturday.
Ridden by Jose Ortiz, Tapwrit ran 1 1/2 miles in 2:30.02 on his home track. Ortiz’s brother Irad Jr. won the race last year with Creator.
Pletcher took two of the year’s three Triple Crown races, having saddled Always Dreaming to victory in the Derby.
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