Simulator starter · reviewed 2026-08-20
Bell State
Two-qubit entanglement demo that shows the shortest public path from visual circuit to generated source, counts, and evidence.
- Qubits
- 2
- Operations
- 4
- Shots
- 4,096
Prepare
Create superposition on q0 and entangle q1 with CNOT.
visual circuit + operation list
Generate
Keep Qiskit and OpenQASM 3 representations inspectable.
generated source
Simulate
Execute 4,096 seeded shots on local Aer.
complete counts + trace
Review
Explain the correlation and the proof boundary.
evidence manifest
Workflow question
What this sample is testing.
Prepare the two-qubit Bell state (|00> + |11>)/sqrt(2), measure both qubits, and preserve enough context for another person to inspect how the result was produced.
Route rationale
Local Qiskit Aer simulator, no provider token required
Complete 4,096-shot 00/11 distribution in a reviewer-safe result packet
Method
Start both qubits in |0>. Apply a Hadamard gate to q0 to create an equal superposition, then use q0 as the control of a CNOT targeting q1. Measure both qubits into two classical bits.
Run the generated Qiskit circuit on the local Qiskit Aer simulator for 4,096 shots with simulator and transpiler seed 2048. Store the circuit, source, complete counts, route note, and export manifest together.
How to read the result
The stored simulator snapshot contains only 00 and 11, with 2,024 and 2,072 observations respectively. That is the correlated computational-basis pattern expected from this ideal Bell-state circuit.
The useful workflow result is not just the chart. It is the link between the visual operations, generated source, simulator configuration, counts, and reviewer-safe evidence record.
Measured distribution
Complete seeded count table
4,096 shots
Complete ideal-simulator distribution. Engine Qiskit Aer 0.17.0; simulator and transpiler seed 2048. This static public fixture is not a live provider run.
Proof boundary
- 01This is a seeded ideal-simulator fixture, not a live hardware result and not evidence of provider performance.
- 02Computational-basis counts alone show correlation but do not by themselves establish entanglement. A stronger experiment should add complementary-basis observables or tomography.
- 03Bit ordering must be checked when comparing Qiskit counts with another SDK or a hardware provider.
Generated representations
Inspect the source behind the counts.
The public code is a review fixture. Provider credentials, workspace members, billing context, and private notes stay excluded.
Qiskit circuit
from qiskit import QuantumCircuit
qc = QuantumCircuit(2, 2)
qc.h(0)
qc.cx(0, 1)
qc.measure([0, 1], [0, 1])OpenQASM circuit
OPENQASM 3;
include "stdgates.inc";
bit[2] c;
qubit[2] q;
h q[0];
cx q[0], q[1];
c[0] = measure q[0];
c[1] = measure q[1];Evidence manifest
{
"workflowId": "QF-SAMPLE-BELL",
"runner": "qiskit-aer",
"artifacts": [
"generated-qiskit.py",
"generated-openqasm.qasm",
"counts.json",
"counts.csv",
"trace.json"
],
"privateFieldsExcluded": [
"providerCredentialId",
"userEmail",
"billingState",
"adminNotes"
]
}What the reviewer receives
- generated-qiskit.py
- generated-openqasm.qasm
- counts.json
- counts.csv
- trace.json
Explicitly excluded
- providerCredentialId
- userEmail
- billingState
- adminNotes
Questions this record answers
Workflow FAQ
What result should a Bell-state circuit produce?
In an ideal computational-basis simulation of this circuit, only 00 and 11 should appear, with approximately half of the shots in each state.
Do Bell-state counts prove entanglement?
Not alone. They show strong correlation in one basis. Complementary-basis observables, a Bell test, or state tomography is needed for a stronger entanglement claim.
Did this sample run on quantum hardware?
No. It is a public, seeded Qiskit Aer simulator fixture and is labeled that way throughout the workflow record.