Triple
T1768275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isola Comacina |
E38813
|
entity |
| Predicate | wasDestroyedInEvent |
P11808
|
FINISHED |
| Object | destruction of 1169 |
—
|
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: destruction of 1169 | Statement: [Isola Comacina, wasDestroyedInEvent, destruction of 1169]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasDestroyedInEvent Context triple: [Isola Comacina, wasDestroyedInEvent, destruction of 1169]
-
A.
destroyedDuring
chosen
Indicates that one entity was destroyed in the course of, or as a consequence of, a specified event or time period.
-
B.
hasCauseOfDestruction
Indicates that one entity is the cause or agent responsible for the destruction or damage of another entity.
-
C.
damagedBy
Indicates that one entity has caused harm, impairment, or deterioration to another entity.
-
D.
dateDestroyed
Indicates the specific date on which an entity was destroyed or ceased to exist.
-
E.
dissipatedOn
Indicates that something (such as energy, force, or a substance) is dispersed, lost, or converted into a less usable form on or within a particular medium, surface, or system.
- 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_69a8862e61708190af97b9838cc3f5de |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab39fc2c448190bfaf1ee8d474632a |
completed | March 6, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69aa61cbb1288190a7ba38b61905f578 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.