Triple
T27531158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torrione di Forio |
E694975
|
entity |
| Predicate | threatDefendedAgainst |
P149086
|
FINISHED |
| Object | pirate raids |
—
|
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: pirate raids | Statement: [Torrione di Forio, threatDefendedAgainst, pirate raids]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatDefendedAgainst Context triple: [Torrione di Forio, threatDefendedAgainst, pirate raids]
-
A.
threatContained
Indicates that an identified threat has been successfully neutralized, controlled, or otherwise prevented from causing further harm or escalation.
-
B.
threatTypeEngaged
Indicates that an entity has actively engaged with or responded to a specific type of threat.
-
C.
defends
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
-
D.
threatsDefendedAgainst
chosen
Indicates a relationship where one entity protects another from specific dangers, attacks, or harmful actions.
-
E.
defendedAs
Indicates that one entity is presented, argued, or justified as being equivalent to or serving the role of another entity in a defensive or protective context.
- 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_69ef538608b081908b9f659bb09d5e0f |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 1:26 p.m.