Triple
T31414774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Davisian model of landscape development |
E801362
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | theory of landscape evolution |
C51360
|
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: theory of landscape evolution Context triple: [Davisian model of landscape development, instanceOf, theory of landscape evolution]
-
A.
loess landform
A loess landform is a landscape shaped by thick deposits of wind-blown, fine-grained silt that create fertile, easily eroded hills, cliffs, and plains.
-
B.
geological model
chosen
A geological model is a conceptual or computational representation of the Earth's subsurface that integrates geological data and interpretations to describe the distribution and properties of rocks, structures, and fluids in three dimensions (and sometimes through time).
-
C.
erosional landscape
An erosional landscape is a terrain shaped primarily by the removal and transport of soil and rock by agents such as water, wind, ice, and gravity, resulting in features like valleys, canyons, and cliffs.
-
D.
travertine terrace formation
A travertine terrace formation is a stepped, layered landscape feature created when mineral-rich hot spring or river waters precipitate calcium carbonate, building natural pools and rimstone dams over time.
-
E.
post-glacial landscape
A post-glacial landscape is a terrain shaped and modified by the advance and retreat of glaciers, characterized by features such as moraines, drumlins, eskers, kettle lakes, and newly exposed soils and bedrock.
- 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_69f348c0dd648190bf2fd7642f78eb06 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 8:42 p.m.