Triple
T32916163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basin and Range–Colorado Plateau transition |
E842017
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tectonic transition zone |
C7693
|
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: tectonic transition zone Context triple: [Basin and Range–Colorado Plateau transition, instanceOf, tectonic transition zone]
-
A.
tectonic province
A tectonic province is a large region of the Earth's crust characterized by a distinct and relatively uniform structural style, geologic history, and tectonic setting.
-
B.
active tectonic zone
An active tectonic zone is a region of the Earth's crust where tectonic plates are currently interacting through processes such as collision, subduction, or sliding past one another, resulting in frequent earthquakes, volcanism, and crustal deformation.
-
C.
transition zone
chosen
A transition zone is a boundary region where two distinct systems, phases, or environments meet and gradually change into one another, exhibiting mixed or intermediate characteristics.
-
D.
tectonostratigraphic province
A tectonostratigraphic province is a region of the Earth's crust characterized by a distinct, internally consistent package of rock units and structures that share a common tectonic and stratigraphic history, setting it apart from adjacent areas.
-
E.
tectonic plate
A tectonic plate is a massive, rigid segment of Earth's lithosphere that moves slowly over the asthenosphere, interacting with other plates to shape the planet's surface through processes like earthquakes, volcanism, and mountain building.
- 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:19 a.m.