Triple
T24014357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reynolds-averaged Navier–Stokes turbulence modeling |
E594627
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | computational fluid dynamics method |
C23145
|
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: computational fluid dynamics method Context triple: [Reynolds-averaged Navier–Stokes turbulence modeling, instanceOf, computational fluid dynamics method]
-
A.
turbulence model
chosen
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.
-
B.
Lagrangian turbulence model
A Lagrangian turbulence model is a computational approach that simulates turbulent flows by tracking the trajectories and interactions of individual fluid particles or parcels over time.
-
C.
fluid dynamics problem
A fluid dynamics problem is a conceptual scenario involving the motion and interaction of fluids (liquids or gases) governed by physical laws such as conservation of mass, momentum, and energy, often expressed through differential equations.
-
D.
fluid dynamicist
A fluid dynamicist is a scientist or engineer who studies and models the behavior of liquids and gases in motion to understand and predict flow phenomena.
-
E.
computational tool
A computational tool is a software or hardware resource designed to perform, automate, or assist with data processing, analysis, or problem-solving tasks.
- 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_69e288bc8f608190ac4af29f0bd1c744 |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 9:42 p.m.