Triple
T14672719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amatrice |
E344551
|
entity |
| Predicate | preEarthquakeFeature |
P115285
|
FINISHED |
| Object | medieval historic center |
—
|
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: medieval historic center | Statement: [Amatrice, preEarthquakeFeature, medieval historic center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preEarthquakeFeature Context triple: [Amatrice, preEarthquakeFeature, medieval historic center]
-
A.
earthquakeType
Indicates the specific classification or category of an earthquake based on its characteristics or cause.
-
B.
hasEarthquakes
Indicates that the specified location or region experiences one or more earthquakes.
-
C.
earthquakeFault
Indicates that one entity is a geological fault associated with, or responsible for, the occurrence of an earthquake affecting the other entity.
-
D.
seismicEvent
Indicates the occurrence of a naturally or artificially induced ground-shaking event, such as an earthquake or tremor, at a specific place and time.
-
E.
foreshocks
Indicates that an earthquake occurs as a smaller, preceding seismic event that happens before a larger mainshock in the same region.
- 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb55064cc8190b9669d0b2da61825 |
completed | April 14, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:27 a.m.