Triple
T35496437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lavic Lake fault |
E1025877
|
entity |
| Predicate | hasSurfaceRupture |
P106756
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lavic Lake fault, hasSurfaceRupture, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurfaceRupture Context triple: [Lavic Lake fault, hasSurfaceRupture, true]
-
A.
surfaceRupture
chosen
Indicates that a geological fault movement has broken through to and displaced the Earth's surface.
-
B.
hasLastMajorSurfaceRuptureIn
Indicates that an entity experienced its most recent significant surface-rupturing event within a specified time or temporal interval.
-
C.
hasSeismicGap
Indicates a segment within a fault or seismic zone where little or no recent earthquake activity has occurred compared to adjacent segments, suggesting accumulated strain and potential for future earthquakes.
-
D.
rupturedFaultSystem
Indicates that a seismic event has caused a fault system to break and slip along one or more of its segments.
-
E.
seismicRuptureLength
Indicates the length of the fault segment that ruptures during a seismic event.
- 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_69f76dfc9c60819089c4217d93922615 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffe01c9d3c819084c256bb3c81c0dc |
completed | May 10, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69ffdfcc78b08190aa4493f13d62a531 |
completed | May 10, 2026, 1:30 a.m. |
Created at: May 3, 2026, 4:04 p.m.