Triple
T27025444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navier boundary condition |
E680771
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | partial slip boundary condition |
C26449
|
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 slip boundary condition Context triple: [Navier boundary condition, instanceOf, partial slip boundary condition]
-
A.
boundary condition
chosen
A boundary condition specifies the behavior or constraints imposed on the edges or limits of a system, domain, or problem space to ensure a well-defined and solvable model.
-
B.
free boundary problem
A free boundary problem is a type of mathematical or physical problem in which the shape or position of the boundary of the domain is not known in advance and must be determined as part of the solution.
-
C.
boundary value problem
A boundary value problem is a mathematical problem in which a differential equation is solved subject to specified conditions (boundary values) imposed on the solution at the boundaries of the domain.
-
D.
turbulence model
A turbulence model is a mathematical framework used in fluid dynamics to approximate the effects of turbulent flow on momentum, energy, and other transported quantities without resolving all turbulent scales directly.
-
E.
fluid flow regime
A fluid flow regime is a conceptual classification of fluid motion characterized by distinct patterns of velocity, pressure, and turbulence behavior under specific flow conditions.
- 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_69eeeb5450988190bfc9a3c012ac463a |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 27, 2026, 7:10 a.m.