Triple
T13339283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castello Ursino |
E317780
|
entity |
| Predicate | survivedNaturalDisaster |
P56127
|
FINISHED |
| Object | earthquake |
—
|
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: earthquake | Statement: [Castello Ursino, survivedNaturalDisaster, earthquake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivedNaturalDisaster Context triple: [Castello Ursino, survivedNaturalDisaster, earthquake]
-
A.
placeOfEventSurvived
chosen
Indicates the location where an event occurred from which the subject successfully survived.
-
B.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
-
C.
survivesShipwreck
Indicates that an entity continues to live or remain alive after experiencing a shipwreck.
-
D.
disasterDepicted
Indicates that one entity visually represents or portrays a disaster involving or affecting another entity.
-
E.
survivedEvent
Indicates that an entity continued to live or exist after experiencing and not being destroyed or killed by a particular 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99d01bf8481908cd3a99e5557b972 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6e53d88190bd6aa42f69b10ffb |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:31 p.m.