Triple
T4094250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Courant–Friedrichs–Lewy condition |
E87775
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | numerical stability condition |
C15253
|
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: numerical stability condition Context triple: [Courant–Friedrichs–Lewy condition, instanceOf, numerical stability condition]
-
A.
astrophysical stability criterion
An astrophysical stability criterion is a theoretical condition or set of conditions used to determine whether an astronomical system (such as a star, disk, or gas cloud) will remain in equilibrium or undergo collapse, fragmentation, or other dynamical instabilities.
-
B.
stability concept in functional equations
A stability concept in functional equations studies how small deviations from an exact functional relationship affect the existence and form of nearby exact solutions, typically quantifying when approximate solutions imply true solutions close in some specified sense.
-
C.
time-stepping scheme
A time-stepping scheme is a numerical method that advances the solution of time-dependent equations from one discrete time level to the next.
-
D.
optimality conditions
Optimality conditions are mathematical criteria that must be satisfied by a candidate solution to ensure it is a local or global optimum of an optimization problem.
-
E.
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.
- 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_69aed94425148190be337845d56fac22 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:40 p.m.