Triple
T20864281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irpinia |
E513709
|
entity |
| Predicate | 1980EarthquakeCasualties |
P115284
|
FINISHED |
| Object | over 2700 deaths |
—
|
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: over 2700 deaths | Statement: [Irpinia, 1980EarthquakeCasualties, over 2700 deaths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 1980EarthquakeCasualties Context triple: [Irpinia, 1980EarthquakeCasualties, over 2700 deaths]
-
A.
earthquakeCasualties
chosen
Indicates that an earthquake event resulted in a specified number or set of casualties (deaths and/or injuries).
-
B.
populationImpact2010Earthquake
Indicates the effect or consequences that the 2010 earthquake had on a population, such as changes in size, distribution, or demographic characteristics.
-
C.
deadliestEarthquakeUntil
Indicates that one earthquake was the most lethal (had caused the highest number of deaths) of all earthquakes up to a specified point in time.
-
D.
notableEarthquake
Indicates that an earthquake event is significant or noteworthy due to its magnitude, impact, or historical importance.
-
E.
facedMajorEarthquake
Indicates that an entity has experienced or been subjected to a significant or severe earthquake event.
- 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.