Triple
T27116459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charleston Seismic Zone |
E686858
|
entity |
| Predicate | hasAftershockActivity |
P3828
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Charleston Seismic Zone, hasAftershockActivity, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAftershockActivity Context triple: [Charleston Seismic Zone, hasAftershockActivity, yes]
-
A.
aftershockCount
Indicates the number of aftershocks that occur following a primary seismic event.
-
B.
aftershocks
chosen
Indicates that one seismic event occurs as a subsequent, typically smaller tremor following a main earthquake.
-
C.
hasEarthquakes
Indicates that the specified location or region experiences one or more earthquakes.
-
D.
notableAftershockMagnitude
Indicates that the magnitude value corresponds to a particularly significant or noteworthy aftershock following a main seismic event.
-
E.
hasVolcanicActivity
Indicates that the subject exhibits or is associated with ongoing or past volcanic processes, such as eruptions, lava flows, or related geothermal activity.
- 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_69ef148c2b588190afc15b529f7af845 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f624069afc8190916ff8dc2e4a3a1a |
completed | May 2, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 8:56 a.m.