Triple
T17479098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1868 Hayward earthquake |
E425610
|
entity |
| Predicate | surfaceRuptureLength |
P54664
|
FINISHED |
| Object | about 32 km |
—
|
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: about 32 km | Statement: [1868 Hayward earthquake, surfaceRuptureLength, about 32 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceRuptureLength Context triple: [1868 Hayward earthquake, surfaceRuptureLength, about 32 km]
-
A.
seismicRuptureLength
chosen
Indicates the length of the fault segment that ruptures during a seismic event.
-
B.
surfaceRupture
Indicates that a geological fault movement has broken through to and displaced the Earth's surface.
-
C.
rupturedFaultSystem
Indicates that a seismic event has caused a fault system to break and slip along one or more of its segments.
-
D.
maximumCrustalExtension
Indicates the greatest amount of stretching or thinning that the Earth’s crust has undergone in a given region or event.
-
E.
hasLastMajorSurfaceRuptureIn
Indicates that an entity experienced its most recent significant surface-rupturing event within a specified time or temporal interval.
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451be5fd08190aeaa12b3a6d6c6d4 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.