Triple
T15570912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A First Course in Turbulence |
E374236
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fluid mechanics textbook |
C22858
|
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: fluid mechanics textbook Context triple: [A First Course in Turbulence, instanceOf, fluid mechanics textbook]
-
A.
fluid dynamics literature
chosen
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.
-
B.
fluid mechanics concept
A fluid mechanics concept is an abstract principle or model that describes how fluids (liquids and gases) behave and interact under various forces, motions, and boundary conditions.
-
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.
foundational work in fluid mechanics
Foundational work in fluid mechanics establishes the core principles, governing equations, and conceptual frameworks that describe how fluids move and interact with forces and boundaries.
-
E.
hydrology textbook
A hydrology textbook is an educational resource that systematically explains the occurrence, distribution, movement, and properties of water on and beneath the Earth's surface, often including theoretical principles, analytical methods, and practical applications.
- 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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 4:10 a.m.