Triple
T22868227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States physiographic regions system |
E567115
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | physiographic classification system |
C33781
|
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: physiographic classification system Context triple: [United States physiographic regions system, instanceOf, physiographic classification system]
-
A.
ecoregion classification system
chosen
An ecoregion classification system is a structured framework that categorizes geographic areas into distinct ecological regions based on shared environmental conditions, ecosystems, and biodiversity patterns.
-
B.
public land classification
Public land classification is the systematic categorization of government-owned lands based on their designated uses, protections, and management objectives, such as conservation, recreation, resource extraction, or development.
-
C.
Köppen climate classification
The Köppen climate classification is a widely used system that categorizes the world's climates based on average temperature and precipitation patterns, grouping regions into distinct climate types such as tropical, arid, temperate, continental, and polar.
-
D.
mountain classification
Mountain classification is the conceptual process of categorizing mountains based on attributes such as elevation, prominence, geology, morphology, and regional context.
-
E.
tectonic system
A tectonic system is the interconnected set of processes and structures through which Earth’s lithospheric plates move, interact, and reshape the planet’s surface over geological time.
- 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_69e24589083081908d5694c4fdc80086 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:38 p.m.