Triple
T967297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MONUSCO |
E20864
|
entity |
| Predicate | hasForceInterventionBrigade |
P22255
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [MONUSCO, hasForceInterventionBrigade, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasForceInterventionBrigade Context triple: [MONUSCO, hasForceInterventionBrigade, yes]
-
A.
intervenedIn
Indicates that an entity took action to alter, influence, or interrupt the course of an event, process, or interaction involving other entities.
-
B.
usesIntervention
Indicates that one entity applies, employs, or relies on a specific intervention (such as a treatment, method, or strategy) in relation to another entity or context.
-
C.
enteredIntoForceBy
Indicates that a legal instrument, agreement, or provision became legally effective as a result of an action taken by a specified authority, event, or instrument.
-
D.
hasMilitaryPresence
Indicates that a military force is present in, stationed at, or operating within a particular location or entity.
-
E.
specialForcesInvolved
Indicates that special forces units participate in or are involved in the referenced action, event, or operation.
- F. None of above. chosen
Provenance (4 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_69a493b33d2c81909c52c369d3ca8436 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b43549008190a4d65efdc3bda520 |
completed | March 1, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a42c1481908d940cbe0aefdd3b |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b36064a48190b85c402f32cbadd1 |
completed | March 1, 2026, 9:45 p.m. |
Created at: March 1, 2026, 7:40 p.m.