Triple
T34933362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1992 Landers earthquake |
E1007500
|
entity |
| Predicate | nearbyMajorFaultSystem |
P197493
|
FINISHED |
| Object | San Andreas Fault system |
—
|
NE NERFINISHED |
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: San Andreas Fault system | Statement: [1992 Landers earthquake, nearbyMajorFaultSystem, San Andreas Fault system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyMajorFaultSystem Context triple: [1992 Landers earthquake, nearbyMajorFaultSystem, San Andreas Fault system]
-
A.
rupturedFaultSystem
Indicates that a seismic event has caused a fault system to break and slip along one or more of its segments.
-
B.
majorFaultSystem
Indicates that one geological fault is the primary or most significant fault within a fault system or structural setting.
-
C.
earthquakeFault
Indicates that one entity is a geological fault associated with, or responsible for, the occurrence of an earthquake affecting the other entity.
-
D.
nearSubductionZone
Indicates that one entity is located geographically close to a tectonic subduction zone.
-
E.
locatedOnTectonicBoundary
Indicates that one entity is situated directly on or along the tectonic plate boundary associated with another entity.
- F. None of above. chosen
Provenance (4 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_69f76dc513fc819084a1ff52abbfa5bc |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe96c2647c819082989f11e1ae3d35 |
completed | May 9, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69fe928615448190af939e5a94be55bb |
completed | May 9, 2026, 1:48 a.m. |
| PDg | Predicate description generation | batch_69fe96c0b760819093737292d33df165 |
completed | May 9, 2026, 2:06 a.m. |
Created at: May 3, 2026, 4 p.m.