Triple
T31176255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1980 Irpinia earthquake |
E794757
|
entity |
| Predicate | worstHitProvince |
P144270
|
FINISHED |
| Object | Avellino |
—
|
NE NERFINISHED |
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: Avellino | Statement: [1980 Irpinia earthquake, worstHitProvince, Avellino]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worstHitProvince Context triple: [1980 Irpinia earthquake, worstHitProvince, Avellino]
-
A.
baseProvince
Indicates that one administrative or territorial unit serves as the primary or originating province associated with another entity.
-
B.
endProvince
Indicates that an entity marks the boundary or final extent of a province within a larger territorial or administrative structure.
-
C.
isProvinceOf
Indicates that one region holds the administrative status of a province within, and is governed as a subnational division of, another political entity.
-
D.
destinationProvince
Indicates the province that serves as the endpoint or target location of a movement, transfer, or route.
-
E.
affectedProvince
chosen
Indicates that a particular province is impacted or influenced by a specified event, action, or condition.
- 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_69f224d5b9708190b6ca79ad2fd3a28a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:08 p.m.