Definition: You are given a background paragraph that describes one or more causal or physical relationships, such as a relationship in economics, scientific law, or nature. You need to come up with a fictional story that makes use of the concepts or the relationship described in the provided paragraph. Make sure that your story does not repeat the relation in the given paragraph (e.g., by avoiding verbatim copies of the given paragraph). Start by reading the background paragraph, and determine what relationship(s) are in the paragraph. Write a story that involves the relationship(s) that you determined are in the background paragraph. Try to use your own words as much as possible and not repeat the background paragraph. Feel free to make up places and events as long as they tie back to the background paragraph in a way that you can ask a question about.

Positive Example 1 -
Input: Background Paragraph: A rise in price of a good or service almost always decreases the quantity demanded of that good or service. Conversely, a fall in price will increase the quantity demanded. When the price of a gallon of gasoline increases, for example, people look for ways to reduce their consumption by combining several errands, commuting by carpool or mass transit, or taking weekend or vacation trips closer to home. Economists call this inverse relationship between price and quantity demanded the law of demand. The law of demand assumes that all other variables that affect demand (which we explain in the next module) are held constant.
Output: The AAA auto club does a weekly report on the prices of gas and diesel in various cities. Historically, the prices have be fairly stagnant, but this week their report garnered widespread attention as the prices of gas and diesel plunged from last week in Seattle by $0.40 each. However, just across the border in Vancouver, the cost of gas went up dramatically by $0.50.

Positive Example 2 -
Input: Background Paragraph: The lesson is not that society is likely to make an extreme choice like devoting no resources to education at point A or no resources to health at point F. Instead, the lesson is that the gains from committing additional marginal resources to education depend on how much is already being spent. If on the one hand, very few resources are currently committed to education, then an increase in resources used can bring relatively large gains. On the other hand, if a large number of resources are already committed to education, then committing additional resources will bring relatively smaller gains.
Output: The state is deciding where to spend the rest of their budget for education. In an analysis of how districts in the state are spending their annual budgets, auditors found that in district A, most of the money was already being spent on schools. However, in district B, the money was not spent on school, but mostly on transportation.

Negative Example 1 -
Input: Background Paragraph: A rise in price of a good or service almost always decreases the quantity demanded of that good or service. Conversely, a fall in price will increase the quantity demanded. When the price of a gallon of gasoline increases, for example, people look for ways to reduce their consumption by combining several errands, commuting by carpool or mass transit, or taking weekend or vacation trips closer to home. Economists call this inverse relationship between price and quantity demanded the law of demand. The law of demand assumes that all other variables that affect demand (which we explain in the next module) are held constant.
Output: A rise in price of a good or service almost always decreases the quantity demanded of that good or service.

Now complete the following example -
Input: Background Paragraph: Storing large volumes of data – When storing XML to either file or database, the volume of data a system produces can often exceed reasonable limits, with a number of detriments: the access times go up as more data is read, CPU load goes up as XML data takes more power to process, and storage costs go up. By storing XML data in Fast Infoset format, data volume may be reduced by as much as 80 percent.
Output: 



Stories:
Adam had a busy day storing XML. At 4 PM, he stored 20 Gigabytes to the database. At 5 PM, he stored 25 Gigabytes to the database. At 6 PM, he stored 30 Gigabytes to the database. At 7 PM, he got dinner. At 8 PM, he stored 35 Gigabytes to the database. At 9 PM, he stored 40 Gigabytes to the database. At 10 PM, he went to sleep to finish storing XML tomorrow.

Antwan had a busy day storing XML. In the morning, he filled up a hard drive with XML. In the afternoon, he filled up a few hard drives with XML. At night, he filled up many hard drives with XML.

Bob had a busy day storing XML. At 1 PM, he stored 15 Gigabytes to the database. At 2 PM, he stored 25 Gigabytes to the database. At 3 PM, he stored 35 Gigabytes to the database. At 4 PM, he got dinner. At 5 PM, he stored 45 Gigabytes to the database. At 6 PM, he stored 55 Gigabytes to the database. At 7 PM, he went to sleep to finish storing XML tomorrow.

Bob works for a data storage company. He has now three projects, project A, project B, and project C, simultaneously going on. All of them involves storing 
XML data. Project A has small volume of data, but project B and project C has large volume of data. He applied Fast Infoset format for project B, but didn't apply that format for project C.

Bradly had a busy day storing XML. At 6 AM, he stored 200 Gigabytes to the database. At 7 AM, he stored 300 Gigabytes to the database. At 8 AM, he stored 400 Gigabytes to the database. At 9 AM, he got breakfast. At 10 AM, he stored 500 Gigabytes to the database. At 11 AM, he stored 600 Gigabytes to the database. At 12 PM, she went to sleep to finish storing XML later.

Brett had a busy day storing XML. At 3 PM, he stored 100 Gigabytes to the database. At 4 PM, he stored 200 Gigabytes to the database. At 5 PM, he stored 300 Gigabytes to the database. At 6 PM, he got dinner. At 7 PM, he stored 400 Gigabytes to the database. At 8 PM, he stored 500 Gigabytes to the database. At 9 PM, he went to sleep to finish storing XML in the morning.

Carl had a busy day storing XML. At 1 PM, he stored 1000 Gigabytes to the database. At 2 PM, he stored 2000 Gigabytes to the database. At 3 PM, he stored 3000 Gigabytes to the database. At 4 PM, he got dinner. At 5 PM, he stored 4000 Gigabytes to the database. At 6 PM, he stored 5000 Gigabytes to the database. At 7 PM, he went to sleep to finish storing XML tomorrow.

Dan had a busy day storing XML. At 2 PM, he stored 10000 Gigabytes to the database. At 3 PM, he stored 20000 Gigabytes to the database. At 4 PM, he stored 30000 Gigabytes to the database. At 5 PM, he got dinner. At 6 PM, he stored 40000 Gigabytes to the database. At 7 PM, he stored 50000 Gigabytes to the database. At 8 PM, he went to sleep to finish storing XML in the morning.

Earl had a busy day storing XML. At 3 PM, he stored 11000 Gigabytes to the database. At 4 PM, he stored 22000 Gigabytes to the database. At 5 PM, he stored 33000 Gigabytes to the database. At 6 PM, he got dinner. At 7 PM, he stored 44000 Gigabytes to the database. At 8 PM, he stored 55000 Gigabytes to the database. At 9 PM, he went to sleep to finish storing XML tomorrow morning.

Eliseo had a busy day storing XML. In the morning, he filled up many hard drives with XML. In the afternoon, he filled up a few hard drives with XML. At night, he filled up a hard drive with XML.

Gary had a lot of storing to do on his computer. At 1 PM, he stored 1 Gigabyte of XML data to the main file. At 2 PM, he stored 2 Gigabytes of XML data to the main file. At 3 PM, he didn't store anything. At 4 PM, he stored 3 Gigabytes of XML data to the main file. At 5 PM, he stored 4 Gigabytes of XML data to the main file. At 6 PM, he did nothing. At 7 PM, he got dinner. At 8 PM, he stored 5 Gigabytes of XML data to the main file.

Gary had a lot of storing to do on his computer. At 1 PM, he stored 1 Gigabyte of XML data to the main file. At 2 PM, he stored 2 Gigabytes of XML data to the main file. At 3 PM, he didn't store anything. At 4 PM, he stored 3 Gigabytes of XML data to the main file. At 5 PM, he stored 4 Gigabytes of XML data to the main file. At 6 PM, he did nothing. At 7 PM, he got dinner. At 8 PM, he stored 5 Gigabytes of XML data to the main file. He went to sleep at 9 PM and had to start again in the morning.

Ian had a busy day storing XML. At 4 PM, he stored 11100 Gigabytes to the database. At 5 PM, he stored 22200 Gigabytes to the database. At 6 PM, he stored 33300 Gigabytes to the database. At 7 PM, he got dinner. At 8 PM, he stored 44400 Gigabytes to the database. At 9 PM, he stored 55500 Gigabytes to the database. At 10 PM, he went to sleep to finish storing XML in the morning.

Joel had a busy day storing XML. At 5 PM, he stored 11110 Gigabytes to the database. At 6 PM, he stored 22220 Gigabytes to the database. At 7 PM, he stored 33330 Gigabytes to the database. At 8 PM, he got dinner. At 9 PM, he stored 44440 Gigabytes to the database. At 10 PM, he stored 55550 Gigabytes to the database. At 11 PM, he went to sleep to finish storing XML tomorrow.

Kenny had a busy day storing XML. At 1 PM, he stored 11111 Gigabytes to the database. At 2 PM, he stored 22222 Gigabytes to the database. At 3 PM, he stored 33333 Gigabytes to the database. At 4 PM, he got dinner. At 5 PM, he stored 44444 Gigabytes to the database. At 6 PM, he stored 55555 Gigabytes to the database. At 7 PM, he went to sleep to finish storing XML tomorrow morning.

Lavern had a stressful day storing a ton of XML. In the morning, he filled up a hard drive with XML. In the afternoon, he filled up a few hard drives with XML. At night, he filled up many hard drives with XML.

Leroy had a busy day storing XML. At 2 PM, he stored 21111 Gigabytes to the database. At 3 PM, he stored 32222 Gigabytes to the database. At 4 PM, he stored 43333 Gigabytes to the database. At 5 PM, he got dinner. At 6 PM, he stored 54444 Gigabytes to the database. At 7 PM, he stored 65555 Gigabytes to the database. At 8 PM, he went to sleep to finish storing XML in the morning.

Odis had a busy day storing XML. At 8 AM, he stored 202 Gigabytes to the database. At 9 AM, he stored 302 Gigabytes to the database. At 10 AM, he stored 402 Gigabytes to the database. At 11 AM, he got breakfast. At 12 PM, he stored 502 Gigabytes to the database. At 1 PM, he stored 602 Gigabytes to the database. At 2 PM, she went to sleep to finish storing XML later on that night.

Paul had a busy day storing XML. At 3 PM, he stored 22111 Gigabytes to the database. At 4 PM, he stored 33222 Gigabytes to the database. At 5 PM, he stored 44333 Gigabytes to the database. At 6 PM, he got dinner. At 7 PM, he stored 55444 Gigabytes to the database. At 8 PM, he stored 66555 Gigabytes to the database. At 9 PM, he went to sleep to finish storing XML tomorrow afternoon.

Paula had a busy day storing XML. At 4 AM, he stored 222 Gigabytes to the database. At 5 AM, he stored 333 Gigabytes to the database. At 6 AM, he stored 444 Gigabytes to the database. At 7 AM, he got breakfast. At 8 AM, he stored 555 Gigabytes to the database. At 9 AM, he stored 666 Gigabytes to the database. At 10 AM, he went to sleep to finish storing XML later at night.

Porfirio had a busy day storing XML. At 9 AM, he stored 203 Gigabytes to the database. At 10 AM, he stored 303 Gigabytes to the database. At 11 AM, he stored 403 Gigabytes to the database. At 12 PM, he got lunch. At 1 PM, he stored 503 Gigabytes to the database. At 2 PM, he stored 603 Gigabytes to the database. At 3 PM, he went to sleep to finish storing XML later that night.

Porfirio had a busy day storing XML. At 9 AM, he stored 203 Gigabytes to the database. At 10 AM, he stored 303 Gigabytes to the database. At 11 AM, he stored 403 Gigabytes to the database. At 12 PM, he got lunch. At 1 PM, he stored 503 Gigabytes to the database. At 2 PM, he stored 603 Gigabytes to the database. At 3 PM, she went to sleep to finish storing XML later that night.

Robin had a busy day storing XML. At 5 AM, he stored 220 Gigabytes to the database. At 6 AM, he stored 330 Gigabytes to the database. At 7 AM, he stored 440 Gigabytes to the database. At 8 AM, he got breakfast. At 9 AM, he stored 550 Gigabytes to the database. At 10 AM, he stored 660 Gigabytes to the database. At 11 AM, she went to sleep to finish storing XML later that day.

Roger had a busy day storing XML. At 4 PM, he stored 22211 Gigabytes to the database. At 5 PM, he stored 33322 Gigabytes to the database. At 6 PM, he stored 44433 Gigabytes to the database. At 7 PM, he got dinner. At 8 PM, he stored 55544 Gigabytes to the database. At 9 PM, he stored 66655 Gigabytes to the database. At 10 PM, he went to sleep to finish storing XML tomorrow.

Samuel had a busy day storing XML. At 5 PM, he stored 223 Gigabytes to the database. At 6 PM, he stored 334 Gigabytes to the database. At 7 PM, he stored 445 Gigabytes to the database. At 8 PM, he got dinner. At 9 PM, he stored 556 Gigabytes to the database. At 10 PM, he stored 667 Gigabytes to the database. At 11 PM, he went to sleep to finish storing XML tomorrow.

Tom had a busy day storing XML. At 2 PM, he stored 10 Gigabytes to the database. At 3 PM, he stored 20 Gigabytes to the database. At 4 PM, he stored 30 Gigabytes to the database. At 5 PM, he got dinner. At 6 PM, he stored 40 Gigabytes to the database. At 7 PM, he stored 50 Gigabytes to the database. At 8 PM, he went to sleep to finish storing XML in the morning.

Tommy had a busy day storing XML. At 3 AM, he stored 224 Gigabytes to the database. At 4 AM, he stored 335 Gigabytes to the database. At 5 AM, he stored 446 Gigabytes to the database. At 6 AM, he got breakfast. At 7 AM, he stored 557 Gigabytes to the database. At 8 AM, he stored 668 Gigabytes to the database. At 9 AM, he went to sleep to finish storing XML later.

Tory had a busy day storing XML. At 7 AM, he stored 201 Gigabytes to the database. At 8 AM, he stored 301 Gigabytes to the database. At 9 AM, he stored 401 Gigabytes to the database. At 10 AM, he got breakfast. At 11 AM, he stored 501 Gigabytes to the database. At 12 PM, he stored 601 Gigabytes to the database. At 1 PM, she went to sleep to finish storing XML later on that day.