Triple
T30397157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greendale Fault |
E773248
|
entity |
| Predicate | seismogenicDepthRange |
P114643
|
FINISHED |
| Object | shallow crustal |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: shallow crustal | Statement: [Greendale Fault, seismogenicDepthRange, shallow crustal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seismogenicDepthRange Context triple: [Greendale Fault, seismogenicDepthRange, shallow crustal]
-
A.
typicalFocalDepthRange
chosen
Indicates the usual range of depths at which an event or phenomenon (such as an earthquake) most commonly occurs below the surface.
-
B.
earthquakeMagnitudeRange
Indicates the range of magnitudes within which an earthquake’s measured strength falls.
-
C.
subductionRate
Indicates the rate at which one tectonic plate moves beneath another into the mantle along a subduction zone.
-
D.
earthquakeFault
Indicates that one entity is a geological fault associated with, or responsible for, the occurrence of an earthquake affecting the other entity.
-
E.
maximumDepthKilometres
Indicates the greatest depth, measured in kilometers, that something reaches or extends to.
- F. None of above.
Provenance (3 batches)
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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f685aef340819081190a2397b94251 |
completed | May 2, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:03 p.m.