Triple
T1218121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulf of Oman |
E26153
|
entity |
| Predicate | hasSecurityIssues |
P3249
|
FINISHED |
| Object | maritime piracy risk |
—
|
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: maritime piracy risk | Statement: [Gulf of Oman, hasSecurityIssues, maritime piracy risk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecurityIssues Context triple: [Gulf of Oman, hasSecurityIssues, maritime piracy risk]
-
A.
majorSecurityIssue
chosen
Indicates that the subject faces or causes a significant security vulnerability or threat.
-
B.
hasSecurityNotion
Indicates that one entity possesses, defines, or is associated with a particular concept or notion of security in relation to another entity or context.
-
C.
hasSecurityPresence
Indicates that some form of security personnel, system, or measures are present at or associated with an entity or location.
-
D.
hasSecurityArchitecture
Indicates that an entity is associated with or defined by a particular security architecture design or framework.
-
E.
hasSecurityStandard
Indicates that an entity complies with, follows, or is governed by a specified security standard or framework.
- 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_69a4948331fc8190b531ac9bec71c491 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be08157c8190b248bb75b922644f |
completed | March 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69a4bb62a7c08190a79dcb6ff72ac99b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.