Triple
T27116454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charleston Seismic Zone |
E686858
|
entity |
| Predicate | notableEventMagnitudeApprox |
P200316
|
FINISHED |
| Object | 7.0 |
—
|
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: 7.0 | Statement: [Charleston Seismic Zone, notableEventMagnitudeApprox, 7.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEventMagnitudeApprox Context triple: [Charleston Seismic Zone, notableEventMagnitudeApprox, 7.0]
-
A.
notableAftershockMagnitude
Indicates that the magnitude value corresponds to a particularly significant or noteworthy aftershock following a main seismic event.
-
B.
notableEarthquake
Indicates that an earthquake event is significant or noteworthy due to its magnitude, impact, or historical importance.
-
C.
notableAftershockDate
Indicates the date on which a significant aftershock occurred following a primary seismic event.
-
D.
notableTsunamiEvent
Indicates that a tsunami event is of particular significance or prominence, such as being historically important, unusually large, or widely recognized.
-
E.
isMajorEventOf
Indicates that an event is a primary, significant, or defining occurrence within the context of another entity (such as a project, period, or process).
- 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_69ef148c2b588190afc15b529f7af845 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69ff80d9a1d88190a95b1488acd6e2e5 |
completed | May 9, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69ff802ae2dc819093a3cda42b63dcbd |
completed | May 9, 2026, 6:42 p.m. |
| PDg | Predicate description generation | batch_69ff80d8ff208190b9e95d077fd99f78 |
completed | May 9, 2026, 6:45 p.m. |
Created at: April 27, 2026, 8:56 a.m.