Triple
T24377780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 Central Italy earthquakes |
E614524
|
entity |
| Predicate | deadliestShockDate |
P27390
|
FINISHED |
| Object | 2016-08-24 |
—
|
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: 2016-08-24 | Statement: [2016 Central Italy earthquakes, deadliestShockDate, 2016-08-24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deadliestShockDate Context triple: [2016 Central Italy earthquakes, deadliestShockDate, 2016-08-24]
-
A.
deadliestIn
Indicates that something has the highest lethality or causes the most deaths within a specified context, group, or location.
-
B.
wasDeadly
Indicates that an event, action, or condition resulted in death or had the capacity to cause death.
-
C.
dateOfTragedy
chosen
Indicates the specific calendar date on which a tragic event occurred.
-
D.
deadliestFor
Indicates that one entity causes the greatest number of deaths or is most lethal specifically with respect to another entity or group.
-
E.
discoveredAsDeadBy
Indicates that one entity was found to be dead by another entity, who discovered their deceased state.
- 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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293d96e7c8190b2f33a8fd12c32c6 |
completed | April 29, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:02 a.m.