Triple
T32620604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maersk Alabama hijacking |
E833909
|
entity |
| Predicate | durationOfHostageSituation |
P142767
|
FINISHED |
| Object | about five days |
—
|
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: about five days | Statement: [Maersk Alabama hijacking, durationOfHostageSituation, about five days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: durationOfHostageSituation Context triple: [Maersk Alabama hijacking, durationOfHostageSituation, about five days]
-
A.
hostageCrisisDuration
chosen
Indicates the length of time that a hostage crisis lasts from its onset to its resolution.
-
B.
durationOfDetention
Indicates the length of time that an entity is or was held in detention.
-
C.
numberOfHostages
Indicates the quantity of hostages involved in a particular situation, event, or context.
-
D.
heldHostagesFor
Indicates that one party unlawfully detained another party or parties as hostages for a period of time, typically to exert pressure or gain leverage.
-
E.
hostageOutcome
Indicates the result or final status of a hostage situation, such as whether hostages were released, rescued, harmed, or remained captive.
- 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_69f3492ccc80819086ef7d26e9786647 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:06 a.m.