Triple
T11053827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shields parameter |
E261323
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sediment transport parameter |
C29086
|
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: sediment transport parameter Context triple: [Shields parameter, instanceOf, sediment transport parameter]
-
A.
sediment transport formula
A sediment transport formula is a mathematical expression that quantifies the rate and mode of sediment movement (bedload, suspended load, or total load) in a fluid flow based on hydraulic and sediment properties.
-
B.
bed-load transport function
A bed-load transport function is a mathematical relationship that predicts the rate at which sediment particles move along a channel bed as a function of flow and sediment characteristics.
-
C.
hydrological system
A hydrological system is the interconnected network of water storage and movement through the atmosphere, land, and water bodies, driven by processes such as precipitation, evaporation, infiltration, and runoff.
-
D.
levee system
A levee system is an integrated network of embankments, floodwalls, and related structures designed to contain or redirect water to protect land and infrastructure from flooding.
-
E.
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.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:26 p.m.