Triple
T20864280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irpinia |
E513709
|
entity |
| Predicate | 1980EarthquakeMagnitude |
P5297
|
FINISHED |
| Object | 6.9 Mw |
—
|
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: 6.9 Mw | Statement: [Irpinia, 1980EarthquakeMagnitude, 6.9 Mw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 1980EarthquakeMagnitude Context triple: [Irpinia, 1980EarthquakeMagnitude, 6.9 Mw]
-
A.
earthquakeMagnitude
chosen
Indicates the measured strength or intensity of an earthquake, typically expressed on a standardized magnitude scale.
-
B.
earthquakeMagnitudeRange
Indicates the range of magnitudes within which an earthquake’s measured strength falls.
-
C.
notableAftershockMagnitude
Indicates that the magnitude value corresponds to a particularly significant or noteworthy aftershock following a main seismic event.
-
D.
lastMajorEarthquakeYear
Indicates the calendar year in which the most recent major earthquake affecting the referenced entity occurred.
-
E.
notableEarthquake
Indicates that an earthquake event is significant or noteworthy due to its magnitude, impact, or historical importance.
- 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_69e0b4f5b01081909452f654d2fc3f50 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c45e51f08190ac1ff59280ad741b |
completed | April 21, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:44 p.m.