Triple
T23202142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Floquet systems |
E580346
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | periodically driven system |
C24870
|
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: periodically driven system Context triple: [Floquet systems, instanceOf, periodically driven system]
-
A.
quantum oscillatory phenomenon
A quantum oscillatory phenomenon is a periodic variation in a measurable quantity arising from the coherent superposition of quantum states, often revealing discrete energy levels or interference effects in a system.
-
B.
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.
-
C.
physical system
chosen
A physical system is a bounded collection of matter, energy, and/or fields whose properties and behavior can be described, analyzed, and predicted using the laws of physics.
-
D.
classical mechanical system
A classical mechanical system is a physical system whose motion and interactions are fully described by Newtonian mechanics (or equivalent formulations like Lagrangian or Hamiltonian mechanics) using deterministic laws for particles or rigid bodies in space and time.
-
E.
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.
- F. None of above.
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_69e24602ae1481908aaa6bc7ca493867 |
completed | April 17, 2026, 2:38 p.m. |
Created at: April 17, 2026, 4:06 p.m.