Triple
T23171761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2012 Emilia earthquakes |
E578878
|
entity |
| Predicate | secondMainshockDate |
P133083
|
FINISHED |
| Object | 2012-05-29 |
—
|
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: 2012-05-29 | Statement: [2012 Emilia earthquakes, secondMainshockDate, 2012-05-29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondMainshockDate Context triple: [2012 Emilia earthquakes, secondMainshockDate, 2012-05-29]
-
A.
secondMajorEarthquakeDate
chosen
Indicates the calendar date on which the second major earthquake in a specified sequence or context occurred.
-
B.
secondAttackDate
Indicates the date on which a second attack or follow-up assault occurred in relation to a prior initial attack.
-
C.
secondAccidentDate
Indicates the date on which a second accident involving the same subject or case occurred.
-
D.
secondCoupDate
Indicates the date on which an entity experienced or carried out its second coup.
-
E.
notableAftershockDate
Indicates the date on which a significant aftershock occurred following a primary seismic 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_69e245fd2a388190b814c0dfa15f7148 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f3007108190bc3c831f81ae1dce |
completed | April 29, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:03 p.m.