Triple
T5099301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book II (Principia) |
E114942
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | treatise on mechanics |
C17570
|
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: treatise on mechanics Context triple: [Book II (Principia), instanceOf, treatise on mechanics]
-
A.
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.
-
B.
Renaissance treatise
A Renaissance treatise is a systematic, often humanist-influenced written work from roughly the 14th to 17th centuries that explores a specific subject—such as art, science, politics, or philosophy—through structured argument and scholarly discourse.
-
C.
branch of mechanics
A branch of mechanics is a specialized subfield of physics that studies the motion and interaction of bodies under the influence of forces within a particular scope or set of assumptions.
-
D.
program of the American Society of Mechanical Engineers
A program of the American Society of Mechanical Engineers is an organized set of activities, initiatives, or services designed to advance mechanical engineering knowledge, practice, standards, and professional development for its members and the broader engineering community.
-
E.
mathematical logic treatise
A mathematical logic treatise is a comprehensive, rigorously structured work that systematically develops the principles, formalisms, and theorems of logic as a branch of mathematics.
- 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_69bd443fc49c819089629c00e311310c |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:40 p.m.