Triple
T6877503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | d’Alembert’s formula |
E158707
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | partial differential equation solution |
C19902
|
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: partial differential equation solution Context triple: [d’Alembert’s formula, instanceOf, partial differential equation solution]
-
A.
partial differential equation
A partial differential equation is an equation that relates the partial derivatives of an unknown multivariable function, describing how it changes with respect to several independent variables.
-
B.
equation in the calculus of variations
An equation in the calculus of variations is a mathematical relation, typically an Euler–Lagrange equation, that characterizes the functions making a given functional stationary (usually minimizing or maximizing its value).
-
C.
evolution equation
An evolution equation is a mathematical expression, typically a differential or integral equation, that describes how a system’s state changes over time according to specified dynamical rules.
-
D.
result in mathematical physics
A result in mathematical physics is a rigorously proven statement that connects precise mathematical structures with physical theories, often clarifying, justifying, or predicting phenomena within a formal framework.
-
E.
solution of classical field equations
chosen
A solution of classical field equations is a specific configuration of fields in space and time that satisfies the governing differential equations and boundary/initial conditions of a classical field theory.
- 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_69c68832af1481908ce356e133ebaebe |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:22 p.m.