Triple
T24377797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 Central Italy earthquakes |
E614524
|
entity |
| Predicate | strongestShockDate |
P46839
|
FINISHED |
| Object | 2016-10-30 |
—
|
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-10-30 | Statement: [2016 Central Italy earthquakes, strongestShockDate, 2016-10-30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strongestShockDate Context triple: [2016 Central Italy earthquakes, strongestShockDate, 2016-10-30]
-
A.
strongestIn
Indicates that one entity possesses the greatest strength or power within a specified group, context, or comparison set.
-
B.
oneOfStrongestEverRecorded
Indicates that something belongs to a very small group of the most powerful or intense instances ever documented or measured.
-
C.
mainshockDate
chosen
Indicates the date on which the primary or largest earthquake event (the mainshock) in a seismic sequence occurred.
-
D.
strongestOver
Indicates that one entity has greater strength or power than all other relevant entities in a given comparison set.
-
E.
strongestInCountrySince
Indicates that something has been the strongest of its kind within a specified country since a particular point in time.
- 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.