Triple
T36870293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R-matrix |
E911206
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fundamental object in integrable systems |
C63394
|
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: fundamental object in integrable systems Context triple: [R-matrix, instanceOf, fundamental object in integrable systems]
-
A.
integrable system
An integrable system is a dynamical system that possesses sufficiently many conserved quantities (integrals of motion) to allow its evolution to be solved exactly, typically through analytic methods such as separation of variables or action-angle coordinates.
-
B.
integrable rigid body system
An integrable rigid body system is a mechanical model of a rigid body whose equations of motion admit enough conserved quantities to be solved exactly, typically allowing its dynamics to be expressed in terms of action-angle variables.
-
C.
integrable top
An integrable top is a rigid body rotating about a fixed point whose equations of motion admit enough conserved quantities to be solved exactly using methods of integrable systems.
-
D.
problem in the theory of Abelian functions
A problem in the theory of Abelian functions concerns questions about the properties, classification, or explicit determination of multivalued complex functions arising from integrals of algebraic differentials on Riemann surfaces and their associated period relations.
-
E.
integral of motion
An integral of motion is a physical quantity that remains constant along the trajectory of a dynamical system due to its underlying symmetries or conservation laws.
- 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_69f76e80f6f0819091cba8e19b269615 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.