Triple
T32694885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maersk Alabama |
E835978
|
entity |
| Predicate | securityChangesAfterEvent |
P7757
|
FINISHED |
| Object | increased armed security on board |
—
|
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: increased armed security on board | Statement: [Maersk Alabama, securityChangesAfterEvent, increased armed security on board]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityChangesAfterEvent Context triple: [Maersk Alabama, securityChangesAfterEvent, increased armed security on board]
-
A.
securityChangesAfter
chosen
Indicates that the security status or configuration of one entity is modified as a consequence of a prior event or change in another entity.
-
B.
hasSecurityEvent
Indicates that a security-related incident or event is associated with, or has occurred for, a given entity.
-
C.
securityModelChange
Indicates that a change has occurred in the security model governing access, permissions, or protection mechanisms between entities.
-
D.
safetyRecordChangedAfter
Indicates that an entity’s safety record was modified following a specified event, time, or condition.
-
E.
safetyChangesImplemented
Indicates that specific safety-related modifications or measures have been put into effect.
- 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_69f3493323288190a4e88251035fe96e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 1, 2026, 1:10 a.m.