user47027: Well basically that. If a transaction is in the memory pool, that is, it is not yet in a block but nodes and miners know about it and validated it, Can I send another transaction that double-spends the outputs? that is, are the outputs considered unspent?

user5406: Let's assume that there are two UTXO under your control, U1 and U2.
You use U1 and U2 to create a transaction T1 that would create U3 when confirmed. U1 and U2 therefore are inputs of the unconfirmed transaction T1 and U3 is an output of T1. 
U1 and U2 are unspent, however another transaction T2 spending either or both of them would be considered a doublespend by any node that knew about T1 before.
Meanwhile, until T1 is confirmed, U3 is not part of the UTXO pool. Since the transaction is yet unconfirmed, the newly created output doesn't exist yet.

user30668: The transactions are considered spent from the nodes that already have the transaction in the mempool, that is, if you try to double-spend the transaction, they will reject the new one. However, if the transaction ends up not being included in a block, they will be dropped from the mempool after a certain time. After that, you will be able to create a new transaction that spends the same UTXOs, since from that point on it won't be considered double-spending. 

47027: <p>Well basically that. If a transaction is in the memory pool, that is, it is not yet in a block but nodes and miners know about it and validated it, Can I send another transaction that double-spends the outputs? that is, are the outputs considered unspent?</p>
 5406: <p>Let's assume that there are two UTXO under your control, <code>U1</code> and <code>U2</code>.</p>

<p>You use <code>U1</code> and <code>U2</code> to create a transaction <code>T1</code> that would create <code>U3</code> when confirmed. <code>U1</code> and <code>U2</code> therefore are <em>inputs</em> of the unconfirmed transaction <code>T1</code> and <code>U3</code> is an output of <code>T1</code>. </p>

<p><code>U1</code> and <code>U2</code> are unspent, however another transaction <code>T2</code> spending either or both of them would be considered a doublespend by any node that knew about <code>T1</code> before.</p>

<p>Meanwhile, until <code>T1</code> is confirmed, <code>U3</code> is not part of the UTXO pool. Since the transaction is yet unconfirmed, the newly created output doesn't exist yet.</p>
 30668: <p>The transactions are considered spent from the nodes that already have the transaction in the <code>mempool</code>, that is, if you try to double-spend the transaction, they will reject the new one. However, if the transaction ends up not being included in a block, they will be dropped from the <code>mempool</code> after a certain time. After that, you will be able to create a new transaction that spends the same <code>UTXOs</code>, since from that point on it won't be considered double-spending. </p>
