sorry to not answer earlier, the question is not that easy but I think I know what happens here.
basically, "entries" does not belong to a certain page. instead, it is a global counter which can be used just by any dimension you want. you would use "page" the most (eg. for a bounce rate calculation), but you can use it for anything else like "language", "login status" or whatever you capture in your dimensions.
now back to your tables: whenever you apply "entries" to a table, it looks what "dimension" you are interested.
filter 1: dimension item
in the first case there are "day" and a certain "page". the number there indicates, how many times the page was the first captured "page" on a given "day" throughout all visits. having a look at the second row you see that you had 37'992 visits on that page and 26'994 "entries" (visits where the "day" / "page" combination was the first that has been captured).
I hope everything is clear until know because now it gets tricky ...
filter 2: hit segment
you changed the way your "entries" counter works in the second table. applying the hit segment with the desired page doesn't have any effect on the "visits", since you are still looking at the same visits (people who visited the page). but now, the "entries" counter has only one "dimension" left to show a number, which is "day". that means as soon as you have the page dimension in the segment, it is not visible for the entries counter anymore. at the end, the counter shows a number, how many times a certain "day" was the entry date of a visit. basically this should be as high as visits, the small difference is due to some midnight breaks... however, the second table the entries does not count for the same as in the first...
I know, this is really tricky, but I hope that I could explain it. let me know if anything is unclear.