You should not copy examples from Firebug. If you do, then you are going to needlessly include classes that jQuery Mobile adds itself. Then, if JQM changes in the future, your markup might be wrong.
(Actually, some developers DO intentionally include the classes that JQM adds. This is to make pages load faster. This is a special technique and isn't generally done, though, and there are some special considerations if you do this. Generally, when we see pages that are "pre-enhanced" it was due to a misunderstanding by the developer.)
Instead, use "view source" so that you are getting pre-enhanced markup as sent by the server. Or, do as suggested above, and copy from the source code for the examples in the git repository.
It's a sad commentary on the state of JQM documentation that developers are tempted to copy examples using Firebug. But there are no examples listed in a form that can be simply copied-and-pasted, and actual, indexed developer documentation is scarce. At least there is now a data-attributes guide, but there is still no guide to the use of classes in JQM. You have to read the CSS files and use Firebug or Web Inspector to interpret. The "documentation" is still just a glorified demo.
As a general rule, you do not use classes to control JQM widgets - except when you do! And, no, the documentation doesn't cover this very well. JQM adds classes based on data- attributes that you supply. In many cases, it also adds tags. This is why you need to examine the enhanced DOM using an inspector any time you write CSS overrides, because classes may not appear on the elements you may think they are applied on. In some cases, though, you DO use classes to control the appearance of a widget.
As for ui-li-static it is applied to list items that do not have an <a> tag. It is used in the CSS to distinguish list items that have links from those that do not.