Triple
T36184760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arnold tongue |
E1046814
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | feature of forced oscillatory systems |
C50713
|
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: feature of forced oscillatory systems Context triple: [Arnold tongue, instanceOf, feature of forced oscillatory systems]
-
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.
electromechanical oscillator
An electromechanical oscillator is a device that converts electrical energy into periodic mechanical motion (and often back into electrical signals), producing sustained oscillations at a characteristic frequency.
-
C.
nonlinear dynamical system
chosen
A nonlinear dynamical system is a system whose evolution over time is governed by equations in which the change of state depends on the current state in a nonlinear way, often leading to complex behaviors such as bifurcations and chaos.
-
D.
magneto-oscillatory effect
The magneto-oscillatory effect is the phenomenon where a material’s electronic or transport properties, such as resistance or magnetization, exhibit periodic oscillations as a function of applied magnetic field due to the quantization of electron orbits.
-
E.
resonance
Resonance is the phenomenon in which a system oscillates with greater amplitude at specific frequencies when subjected to periodic forces matching its natural frequency.
- 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_69f76e3d4fbc81908c159c7beeb4ce00 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.