Triple
T15151161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific Plate fracture zone system |
E361944
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fracture zone system |
C1808
|
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: fracture zone system Context triple: [Pacific Plate fracture zone system, instanceOf, fracture zone system]
-
A.
oceanic fracture zone
chosen
An oceanic fracture zone is a linear, seafloor feature formed by past transform fault activity that offsets and segments mid-ocean ridges, marked by steep escarpments and contrasting crustal ages on either side.
-
B.
fault system
A fault system is a network of related fractures in the Earth's crust along which movement has occurred, collectively accommodating and distributing tectonic strain.
-
C.
fissure system
A fissure system is a network of linear fractures or cracks in the Earth's crust through which magma, fluids, or gases can move and sometimes erupt at the surface.
-
D.
ancient fracture network
An ancient fracture network is a preserved system of interconnected cracks and fractures in rock that formed in the geological past and now influences the rock’s mechanical behavior and fluid flow.
-
E.
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.
- 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_69d85a0759908190b8a051d2e2a1cbe6 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:07 a.m.