increment available Sprint Planning?

Does the increment meet DoD? usable and valuable ?

There is without a doubt an increment available during Sprint Planning.  It would be the last increment delivered from the previous Sprint.  However, I see no way that an increment can be created/completed during Sprint Planning.  

Here is a link to the section that defines an Increment in Scrum from English version of the Scrum Guide. (https://scrumguides.org/scrum-guide.html#increment ). After reading that section, do you see why I made my statement? 

Is there any possibility that increment available during Sprint Planning or at the end?

Yes, however unlikely, because Scrum does not rule it out.

Please let me know if any such example come to any one mind.

Suppose we have a month to develop a comedy show. It's a complex challenge and empiricism will be needed. So we experiment with gags at a tough stand-up venue. If they work there, they'll work anywhere.

Each gag is an MVP experiment that is Done and deliverable. By the end of our Sprint Planning evening we have identified successful gags from which we draw a unifying theme. Developing a show with that theme is our Sprint Goal and we have a forecast of gags in our Sprint Backlog for achieving it.

Why you ask this question? ;)

Another example is that some PBI meets DoD without people doing the work (e.g. automated tests running for a few hours while a team is busy planning the next Sprint). It can even be automatically released. Stopping this process would be a lean waste IMHO.

This would be e.g. a PBI selected for the Sprint that wasn't "done" in the previous Sprint.

Thank you everyone for your input. The origin of this question is what artifacts can be inspected and adapted during the Sprint Planning. I am sure for Product backlog, Sprint Backlog however bit confused with increment. However the above examples shows that every scrum artifact can be inspected and adapted during Sprint Planning.