Triple
T7420017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On the Rotation of a Solid Body About a Fixed Point |
E171221
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | work on rigid body dynamics |
C1873
|
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: work on rigid body dynamics Context triple: [On the Rotation of a Solid Body About a Fixed Point, instanceOf, work on rigid body dynamics]
-
A.
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.
-
B.
joint planning and execution system
A joint planning and execution system is an integrated framework that enables multiple agents or stakeholders to collaboratively create, coordinate, and carry out shared plans toward common goals in dynamic environments.
-
C.
classical mechanics
chosen
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.
-
D.
robot control system
A robot control system is a coordinated set of hardware and software components that interpret sensor data, execute decision-making algorithms, and generate actuator commands to direct a robot’s behavior in real time.
-
E.
robotics research platform
A robotics research platform is a configurable hardware and software system designed to develop, test, and evaluate robotic algorithms, sensors, and control strategies in controlled and repeatable environments.
- 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_69c68a625d048190af70eb8b63bec5a0 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:11 p.m.