Triple
T11398726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | brachistochrone problem |
E270049
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | problem in the calculus of variations |
C7254
|
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: problem in the calculus of variations Context triple: [brachistochrone problem, instanceOf, problem in the calculus of variations]
-
A.
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).
-
B.
necessary conditions for optimality
Necessary conditions for optimality are criteria that any candidate solution must satisfy in order to be considered a potential optimizer (such as a minimum, maximum, or saddle point) of a given objective function under specified constraints.
-
C.
mathematical problem
chosen
A mathematical problem is a question or task that requires the application of mathematical concepts, methods, or reasoning to find a solution or demonstrate a result.
-
D.
problem in invariant theory
A problem in invariant theory concerns determining and characterizing the algebraic functions (invariants) that remain unchanged under the action of a given group on a vector space or algebraic variety.
-
E.
initial value problem
An initial value problem is a type of differential equation together with specified values of the unknown function (and possibly its derivatives) at a starting point, from which a unique solution is sought.
- 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:34 p.m.