Triple
T25493205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taylor–Proudman theorem |
E638888
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | result in geophysical fluid dynamics |
C46000
|
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: result in geophysical fluid dynamics Context triple: [Taylor–Proudman theorem, instanceOf, result in geophysical fluid dynamics]
-
A.
result in atmospheric dynamics
chosen
A result in atmospheric dynamics is a derived outcome—such as a quantified relationship, pattern, or prediction—that explains or characterizes how atmospheric motions and processes evolve under specified physical conditions.
-
B.
rotating fluid body
A rotating fluid body is a continuous mass of fluid that spins around an axis, whose shape, internal flow, and dynamical behavior are governed by the balance of inertial, gravitational, and pressure forces under rotation.
-
C.
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.
-
D.
physical oceanographic system
A physical oceanographic system is the interconnected set of oceanic processes, properties, and structures—such as currents, waves, temperature, and salinity—that govern the movement and distribution of energy and matter in the sea.
-
E.
fluid dynamics literature
Fluid dynamics literature encompasses scholarly and technical writings that analyze, model, and explain the behavior of fluids in motion and at rest across scientific, engineering, and applied contexts.
- 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_69e75dbbd2a88190b70e1e645de14b9a |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 2:39 p.m.