Question: How many states does Australia contain and what are their names?
About the article "Australia", section "States and territories".

Candidate passages:
Articles related to Egyptian mythology.
Note that many synonyms exist for Egyptian deities; what follows is a list of each distinct entry, and does not contain any synonyms of the names for deities.__NOTOC__ 
The "Prose" and "Poetic Eddas", which form the foundation of what we know today concerning Norse mythology, contain many names of Jotnar (giants and giantesses).
While many of them are featured in extant myths of their own, many others have come down to us today only as names in various lists provided for the benefit of skalds or poets of the medieval period and are included here for the purpose of completeness. 
This episode does not contain the "VeggieTales Theme" or "What We Have Learned".
It does include the following songs:  "How to Draw Me", sung by Larry the Cucumber  "President Tim and the Kids", sung by Larry the Cucumber  "We Are Climbing Jacob's Ladder", sung by Jimmy and Jerry Gourd  
A proper name tells us "which" thing is in question, without giving us any other information about it.
But how does it do this?
What exactly is the nature of this information?
There are two puzzles in particular: The name in some way reveals the identity of the object.
An identity statement, such as "Hesperus = Phosphorus" should contain no information at all.
If we understand the names, we should understand the information they carry, namely the identity of their bearers, and if we grasp their identity, we should understand automatically whether the statement is true or false.
Thus the statement should not be informative.
Yet it is.
The discovery that Hesperus = Phosphorus was (in its day) a great scientific achievement.
Empty names have to seem perfectly meaningful.
Then whose identity do they reveal?
If the only semantic function of a name is to tell us which individual a proposition is about, how can it tell us this when there is no such individual?  
Information in a computer file can consist of smaller packets of information (often called "records" or "lines") that are individually different but share some common traits.
For example, a payroll file might contain information concerning all the employees in a company and their payroll details; each record in the payroll file concerns just one employee, and all the records have the common trait of being related to payroll—this is very similar to placing all payroll information into a specific filing cabinet in an office that does not have a computer.
A text file may contain lines of text, corresponding to printed lines on a piece of paper.
Alternatively, a file may contain an arbitrary binary image (a BLOB) or it may contain an executable.
The way information is grouped into a file is entirely up to how it is designed.
This has led to a plethora of more or less standardized file structures for all imaginable purposes, from the simplest to the most complex.
Most computer files are used by computer programs which create, modify or delete the files for their own use on an as-needed basis.
The programmers who create the programs decide what files are needed, how they are to be used and (often) their names.
In some cases, computer programs manipulate files that are made visible to the computer user.
For example, in a word-processing program, the user manipulates document files that the user personally names.
Although the content of the document file is arranged in a format that the word-processing program understands, the user is able to choose the name and location of the file and provide the bulk of the information (such as words and text) that will be stored in the file.
Many applications pack all their data files into a single file called archive file, using internal markers to discern the different types of information contained within.
The benefits of the archive file are to lower the number of files for easier transfer, to reduce storage usage, or just to organize outdated files.
The archive file must often be unpacked before next using.