Triple
T12101014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niger Delta Liberation Front |
E288188
|
entity |
| Predicate | typeOfConflictParty |
P375
|
FINISHED |
| Object | non-state belligerent |
—
|
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: non-state belligerent | Statement: [Niger Delta Liberation Front, typeOfConflictParty, non-state belligerent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfConflictParty Context triple: [Niger Delta Liberation Front, typeOfConflictParty, non-state belligerent]
-
A.
conflictType
Indicates the specific kind or category of conflict that characterizes the relationship or interaction between entities.
-
B.
partnerInConflictWith
Indicates that two entities are engaged as opposing partners or sides within the same conflict or dispute.
-
C.
conflictSide
chosen
Indicates that an entity participates as a distinct party or faction on one side of a conflict or dispute.
-
D.
conflictRole
Indicates that an entity plays a specific role or position within a conflict or dispute between parties.
-
E.
opposesPartyType
Indicates that one party or entity is in opposition to, or acts against the interests or positions of, a particular type or category of party.
- 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_69d6ab4a5c448190a110d1273314b21a |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9178ad99c8190a54777b9bbe998bc |
completed | April 10, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69d915000454819089fee00022055599 |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:48 p.m.