Triple
T23307582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mali–Burkina Faso border region |
E590492
|
entity |
| Predicate | conflictActorPresent |
P6060
|
FINISHED |
| Object | al-Qaeda-affiliated groups |
—
|
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: al-Qaeda-affiliated groups | Statement: [Mali–Burkina Faso border region, conflictActorPresent, al-Qaeda-affiliated groups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictActorPresent Context triple: [Mali–Burkina Faso border region, conflictActorPresent, al-Qaeda-affiliated groups]
-
A.
conflictRole
chosen
Indicates that an entity plays a specific role or position within a conflict or dispute between parties.
-
B.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
C.
partnerInConflictWith
Indicates that two entities are engaged as opposing partners or sides within the same conflict or dispute.
-
D.
formedInConflict
Indicates that an entity came into existence as a direct result of, or during the course of, a specific conflict or war.
-
E.
hasPartOfConflict
Indicates that one conflict includes another conflict as a constituent or subordinate part of it.
- 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_69e25d1c0ecc8190a355aa229f06d0e0 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1972846fc819092ca2b9590b2e177 |
completed | April 29, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 5:05 p.m.