Triple
T1353605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caledonian fault system |
E28937
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tectonic structure |
C6951
|
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 structure Context triple: [Caledonian fault system, instanceOf, tectonic structure]
-
A.
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.
-
B.
major tectonic plate
A major tectonic plate is a large, rigid segment of Earth's lithosphere that moves over the asthenosphere and interacts with other plates to shape the planet's surface through processes like earthquakes, volcanism, and mountain building.
-
C.
lithospheric plate
A lithospheric plate is a rigid, outer shell segment of the Earth’s crust and upper mantle that moves over the more ductile asthenosphere, interacting with other plates at its boundaries to shape the planet’s surface.
-
D.
transform fault system
A transform fault system is a network of strike-slip plate boundaries where tectonic plates slide horizontally past each other along fractures in the Earth's crust, often linking segments of mid-ocean ridges or other plate boundaries.
-
E.
impact structure
An impact structure is a geological formation created by the collision of a meteoroid, asteroid, or comet with a planetary surface, typically characterized by a crater and associated deformation features.
- 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_69a498571d248190a0ac9eb02d97097f |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:56 p.m.