Triple
T32694893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maersk Alabama |
E835978
|
entity |
| Predicate | postHijackingStatus |
P175495
|
FINISHED |
| Object | returned to service after 2009 incident |
—
|
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: returned to service after 2009 incident | Statement: [Maersk Alabama, postHijackingStatus, returned to service after 2009 incident]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postHijackingStatus Context triple: [Maersk Alabama, postHijackingStatus, returned to service after 2009 incident]
-
A.
hijackingEndedBy
Indicates that a hijacking event is brought to an end or terminated by a specified agent or action.
-
B.
hijacked
Indicates that one entity has forcibly taken control of another entity, typically without authorization and against the will of its rightful controller.
-
C.
post2000Status
Indicates whether a given entity’s status, condition, or classification applies specifically to the period after the year 2000.
-
D.
postEventStatus
Indicates the status or condition assigned to an event after it has occurred or been processed.
-
E.
postMergerStatus
Indicates the status or condition of an entity following the completion of a merger.
- 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_69f3493323288190a4e88251035fe96e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d210fc80819091ed8961aa2cddfb |
completed | May 3, 2026, 4:41 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d16b79dc8190ab0d4657f2ef9a5b |
completed | May 3, 2026, 4:39 a.m. |
Created at: May 1, 2026, 1:10 a.m.