Triple
T1353604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caledonian fault system |
E28937
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geological fault system |
C1809
|
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: geological fault system Context triple: [Caledonian fault system, instanceOf, geological fault system]
-
A.
transform fault system
chosen
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.
-
B.
strike-slip fault
A strike-slip fault is a fracture in the Earth's crust where blocks of rock slide horizontally past each other, primarily due to shear stress.
-
C.
geological boundary
A geological boundary is a conceptual division in the Earth's crust that separates distinct rock units, layers, or geological features based on differences in age, composition, structure, or formation history.
-
D.
geological event
A geological event is a natural occurrence resulting from Earth’s internal or surface processes, such as earthquakes, volcanic eruptions, landslides, or tectonic shifts, that alters the planet’s physical structure or landscape.
-
E.
plate boundary
A plate boundary is the region where two or more tectonic plates meet and interact, often causing earthquakes, volcanic activity, 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_69a498571d248190a0ac9eb02d97097f |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:56 p.m.