Triple
T23006193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glauber coherent states |
E572775
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | quantum state |
C47123
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: quantum state Context triple: [Glauber coherent states, instanceOf, quantum state]
-
A.
quantum two-state system
A quantum two-state system is a physical system that can exist in any quantum superposition of two distinct basis states, often used as the simplest model for quantum behavior such as spin-½ particles or qubits.
-
B.
problem in quantum information theory
A problem in quantum information theory is a conceptual or mathematical question concerning how information is represented, processed, transmitted, or measured using quantum mechanical systems and principles.
-
C.
theorem in quantum foundations
A theorem in quantum foundations is a rigorously proven mathematical statement that clarifies or constrains the possible structures, interpretations, or empirical predictions of quantum theory at its most fundamental level.
-
D.
parameter of two-level quantum systems
A parameter of two-level quantum systems is a variable (such as energy splitting, phase, or coupling strength) that characterizes and controls the state evolution and observable properties of a quantum system with two basis states.
-
E.
quantum theory formalism
A quantum theory formalism is a mathematical framework that specifies the states, observables, and dynamical laws governing quantum systems, enabling the prediction of measurement outcomes and their probabilities.
- F. None of above. chosen
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:51 p.m.