Triple
T26345049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euler–Poisson equations |
E662758
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mathematical model in rigid body dynamics |
C22182
|
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: mathematical model in rigid body dynamics Context triple: [Euler–Poisson equations, instanceOf, mathematical model in rigid body dynamics]
-
A.
integrable rigid body system
chosen
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.
-
B.
physical model
A physical model is a tangible, scaled, or otherwise material representation of an object, system, or phenomenon used to study, demonstrate, or predict its real-world behavior.
-
C.
treatise on mechanics
A treatise on mechanics is a systematic, often mathematically grounded work that explains the principles governing motion, forces, and the behavior of physical bodies.
-
D.
classical mechanics
Classical mechanics is the branch of physics that describes the motion of macroscopic objects under the influence of forces using laws such as Newton’s laws of motion and conservation principles.
-
E.
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.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
Created at: April 26, 2026, 10:41 p.m.