Triple
T29918217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ridgecrest fault system |
E759848
|
entity |
| Predicate | earthquakeMechanism |
P28044
|
FINISHED |
| Object | strike-slip faulting |
—
|
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: strike-slip faulting | Statement: [Ridgecrest fault system, earthquakeMechanism, strike-slip faulting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earthquakeMechanism Context triple: [Ridgecrest fault system, earthquakeMechanism, strike-slip faulting]
-
A.
earthquakeFault
Indicates that one entity is a geological fault associated with, or responsible for, the occurrence of an earthquake affecting the other entity.
-
B.
seismicityCause
Indicates that one factor or event is the cause or source of observed seismic activity in another context or location.
-
C.
earthquakeType
chosen
Indicates the specific classification or category of an earthquake based on its characteristics or cause.
-
D.
seismicEvent
Indicates the occurrence of a naturally or artificially induced ground-shaking event, such as an earthquake or tremor, at a specific place and time.
-
E.
earthquakeSequence
Indicates a relationship where multiple earthquakes are linked as part of the same temporal or causal sequence of seismic events.
- 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_69f2246189fc8190996b63ee1f9a2374 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6779140408190987216918cfaf0cb |
completed | May 2, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:13 p.m.