Triple
T32694934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abduwali Muse |
E835979
|
entity |
| Predicate | victimShipType |
P8971
|
FINISHED |
| Object | container ship |
—
|
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: container ship | Statement: [Abduwali Muse, victimShipType, container ship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: victimShipType Context triple: [Abduwali Muse, victimShipType, container ship]
-
A.
victimShipFlag
Indicates that the relationship specifies the national flag or registry under which the victim ship is sailing.
-
B.
shipTypeInvolved
chosen
Indicates that a particular type or class of ship is involved or participates in a specified event, situation, or relationship.
-
C.
shipwreckType
Indicates the specific kind or classification of a shipwreck associated with an entity.
-
D.
capturedShipType
Indicates that one entity has taken possession of another entity’s ship, specifying the type or category of the ship that was captured.
-
E.
shipInvolved
Indicates that a ship participates in, is associated with, or plays a role in a specified event or situation.
- 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_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:10 a.m.