Triple
T23573926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1783 Calabrian earthquakes |
E580193
|
entity |
| Predicate | numberOfMajorShocks |
P153227
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [1783 Calabrian earthquakes, numberOfMajorShocks, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfMajorShocks Context triple: [1783 Calabrian earthquakes, numberOfMajorShocks, 5]
-
A.
aftershockCount
Indicates the number of aftershocks that occur following a primary seismic event.
-
B.
numberOfMajorFalls
Indicates the count of significant or serious falling incidents experienced by an entity within a specified period or context.
-
C.
numberOfMajorHurricanes
Indicates the count of hurricanes within a specified context that reach or exceed the defined intensity threshold for being classified as major.
-
D.
facedMajorEarthquake
Indicates that an entity has experienced or been subjected to a significant or severe earthquake event.
-
E.
notableAftershockMagnitude
Indicates that the magnitude value corresponds to a particularly significant or noteworthy aftershock following a main seismic event.
- F. None of above. chosen
Provenance (4 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_69e24601a9108190bc31e83833c980e4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1afd4cde48190b5e4eb162d772319 |
completed | April 29, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f12760784c8190aaeff002ef31febe |
completed | April 28, 2026, 9:32 p.m. |
Created at: April 17, 2026, 6:37 p.m.