Triple
T8782932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1995 Ouagadougou peace agreement |
E208975
|
entity |
| Predicate | conflictTypeAddressed |
P70218
|
FINISHED |
| Object | internal armed conflict |
—
|
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: internal armed conflict | Statement: [1995 Ouagadougou peace agreement, conflictTypeAddressed, internal armed conflict]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictTypeAddressed Context triple: [1995 Ouagadougou peace agreement, conflictTypeAddressed, internal armed conflict]
-
A.
conflictType
Indicates the specific kind or category of conflict that characterizes the relationship or interaction between entities.
-
B.
addressedConflictWith
Indicates that one entity has taken action to confront, manage, or resolve a conflict involving another entity.
-
C.
addressesConflictWithin
chosen
Indicates that one entity deals with, manages, or resolves a conflict that exists inside another entity or within its internal scope.
-
D.
conflictSpecific
Indicates a specific, concrete instance or type of conflict that exists between the related entities.
-
E.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
- 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_69ca836168108190bb43d3dc235c1f55 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f72f4bc8190b85bd051d3db6881 |
completed | March 31, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1aff3881908be6a9cbc9f50461 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:42 p.m.