Triple
T27116457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charleston Seismic Zone |
E686858
|
entity |
| Predicate | notableEventFeltArea |
P200335
|
FINISHED |
| Object | large area of eastern United States |
—
|
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: large area of eastern United States | Statement: [Charleston Seismic Zone, notableEventFeltArea, large area of eastern United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEventFeltArea Context triple: [Charleston Seismic Zone, notableEventFeltArea, large area of eastern United States]
-
A.
notableEventMagnitudeApprox
Indicates that an associated notable event has an approximate (not exact) magnitude or intensity value.
-
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.
strongShakingAlsoFeltIn
Indicates that intense shaking at one location was also experienced in another location.
-
E.
strongestShakingArea
Indicates the area that experiences the most intense level of shaking relative to surrounding regions.
- 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_69ff84202eb081908ae21a54a4414d68 |
completed | May 9, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69ff833065e4819098579129d4ee17d3 |
completed | May 9, 2026, 6:55 p.m. |
| PDg | Predicate description generation | batch_69ff841f2f2081908d72d4f878c538a0 |
completed | May 9, 2026, 6:59 p.m. |
Created at: April 27, 2026, 8:56 a.m.