Triple
T15322763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Atlantic fracture zone system |
E366333
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | oceanic crustal fault network |
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: oceanic crustal fault network Context triple: [North Atlantic fracture zone system, instanceOf, oceanic crustal fault network]
-
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.
oceanic spreading center
An oceanic spreading center is a linear, submarine plate boundary where tectonic plates diverge and new oceanic crust is created by upwelling and solidification of magma.
-
C.
crustal block
A crustal block is a relatively rigid, coherent segment of the Earth's crust bounded by faults or other discontinuities that can move or deform as a unit within the larger tectonic framework.
-
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.
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.
- 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:16 a.m.