Triple
T32954289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elsinore Fault Zone |
E843052
|
entity |
| Predicate | faultSlipSense |
P27394
|
FINISHED |
| Object | dextral |
—
|
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: dextral | Statement: [Elsinore Fault Zone, faultSlipSense, dextral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: faultSlipSense Context triple: [Elsinore Fault Zone, faultSlipSense, dextral]
-
A.
dominantSlipSense
chosen
Indicates the primary direction or mode in which slip or displacement occurs along a fault or between two surfaces.
-
B.
averageSlipRate
Indicates the typical rate at which displacement or movement occurs along a fault or interface over a specified period of time.
-
C.
surfaceRupture
Indicates that a geological fault movement has broken through to and displaced the Earth's surface.
-
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.
rupturedFaultSystem
Indicates that a seismic event has caused a fault system to break and slip along one or more of its segments.
- 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_69f3494a31f481909057136e49b4fe60 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d17171388190b37fb7268a80b569 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:21 a.m.