Triple
T35496436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lavic Lake fault |
E1025877
|
entity |
| Predicate | seismogenic |
P183355
|
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, seismogenic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seismogenic Context triple: [Lavic Lake fault, seismogenic, true]
-
A.
seismicityCause
Indicates that one factor or event is the cause or source of observed seismic activity in another context or location.
-
B.
seismicSignificance
Indicates the degree to which something is relevant, influential, or important in the context of seismic activity or earthquake-related phenomena.
-
C.
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.
-
D.
seismicMoment
Indicates the relationship between an earthquake event and the total energy it releases, quantified as its seismic moment.
-
E.
seismicMonitoring
Indicates the ongoing observation and measurement of seismic activity or ground motion to detect, record, and analyze earthquakes or related geophysical events.
- 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_69f76dfc9c60819089c4217d93922615 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79da8d8848190ab5ab1bdad95d58c |
completed | May 3, 2026, 7:10 p.m. |
Created at: May 3, 2026, 4:04 p.m.