Triple
T2265177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derna |
E50126
|
entity |
| Predicate | securityIssues |
P3815
|
FINISHED |
| Object | armed groups presence |
—
|
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: armed groups presence | Statement: [Derna, securityIssues, armed groups presence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityIssues Context triple: [Derna, securityIssues, armed groups presence]
-
A.
majorSecurityIssue
Indicates that the subject faces or causes a significant security vulnerability or threat.
-
B.
securityRecommendation
Indicates that one entity advises or prescribes specific security-related actions, settings, or measures for another entity.
-
C.
security
Indicates that an entity provides protection, safety measures, or safeguards to another entity or against specific threats or risks.
-
D.
securityAspect
chosen
Indicates a relationship where something pertains to, represents, or characterizes a particular aspect or dimension of security.
-
E.
securityProgram
Indicates that an entity is associated with, participates in, or is governed by a security program, such as a set of policies, controls, or initiatives related to safety or protection.
- 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_69a88b01e0048190ba96431b5f990ba9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc2ea65288190bc8644a07a11dfa9 |
completed | March 7, 2026, 6:17 a.m. |
| PD | Predicate disambiguation | batch_69abbdb592588190ac1ef5e8c54575b1 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.