Triple
T23283455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Islamic State of the Greater Sahara |
E588926
|
entity |
| Predicate | notableAttackType |
P4333
|
FINISHED |
| Object | cross‑border raids |
—
|
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: cross‑border raids | Statement: [Islamic State of the Greater Sahara, notableAttackType, cross‑border raids]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAttackType Context triple: [Islamic State of the Greater Sahara, notableAttackType, cross‑border raids]
-
A.
notableAttack
Indicates that an entity carried out, was involved in, or is strongly associated with a particularly significant or well-known attack.
-
B.
attackType
chosen
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
C.
notableIncidentType
Indicates the specific category or kind of significant event or incident associated with an entity.
-
D.
notableAttackLocation
Indicates the specific place where a significant or notable attack occurred in relation to the subject.
-
E.
plannedAttack
Indicates that an entity has intentionally prepared and organized an attack against a target.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196447a748190bd797ec9baa63fc3 |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:58 p.m.