I don't think they're technically the same because UNION implicitly removes duplicates.
In the case of your specific data, the queries are probably functionality the same as you probably wouldn't have duplicates in the first query because each row most likely has a unique ID column. Even if it didn't, last-updated and created-at are probably timestamps which would in practice make them unique, not to mention other fields such as headline and article body - unless there had been a glitch causing a row to be inserted twice.
If you were to use UNION ALL in place of UNION, duplicates would no longer be removed from the second query. In that case, even if you had duplicate rows in the first query, the second query would return the same rows unless any rows with ID 1, 2 or 3 also had been updated in the given timespan (as those will now be duplicated by the second query)
Pretty sure that's how UNION works, so in practice, I think you'd get the same rows 99.9% of the time.