Assuming you were using properties that are orderable (such as temporal types, epoc timestamps, or string dates that order correctly, unlike the example you provided), you can add an index on the property in question, and use a range index lookup.
One problem however is that the times you provided do not include the year. All of the time representations I mentioned earlier are absolute, a time representation of an instant, including the year.
If you want a relative time representation, independent of the year, then a String representation might work best instead of the others. For example: "05/10 10:05" (you should be using 24 hour time and not using am/pm so that the times are properly orderable). This would probably be in addition to a proper timestamp, as other use cases would likely work better with an instant of time rather than this year-independent representation.
So, let's say we have nodes like this:
(:Person {relativeDOB:"05/10 10:07"})
Then we would want an index on this:
CREATE index on :Person(relativeDOB)
After we have the index, we can perform an index range lookup:
WITH "05/10 10:05" as start, "05/10 10:10" as end
MATCH (p:Person)
WHERE start <= p.relativeDOB <= end
RETURN count(p) as kidsBornInRange
This is of course regardless of year, just looking at the month/date/time range.
If the actual use case includes the year, then you can disregard most of what I said about year-independent values, and just use regular dateTime or timestamp types instead, the query will be relatively the same, you'll just define the start and end times with the appropriate types.
