Triple
T6474611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1983 Beirut barracks bombings |
E146038
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | attack on peacekeepers |
C20201
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: attack on peacekeepers Context triple: [1983 Beirut barracks bombings, instanceOf, attack on peacekeepers]
-
A.
peacekeeping force
A peacekeeping force is an organized, often multinational group deployed to conflict or post-conflict areas to monitor ceasefires, support political processes, protect civilians, and help maintain or restore peace and security.
-
B.
military intervention
Military intervention is the deliberate use or deployment of a state's armed forces in another state's territory or conflict to influence political, security, or humanitarian outcomes.
-
C.
United Nations peacekeeping mission
A United Nations peacekeeping mission is an international operation authorized by the UN to help maintain or restore peace and security in conflict-affected areas through the deployment of military, police, and civilian personnel under impartial mandates.
-
D.
peacekeeping support mechanism
A peacekeeping support mechanism is a structured system of resources, processes, and coordination tools designed to assist, sustain, and enhance the effectiveness of peacekeeping operations in preventing, managing, and resolving conflicts.
-
E.
peacekeeping support structure
A peacekeeping support structure is an organized framework of logistical, administrative, and operational resources that enables and sustains peacekeeping missions in conflict or post-conflict environments.
- F. None of above. chosen
Provenance (1 batch)
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_69c008fec7408190af7b146dc63d9750 |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 4:50 p.m.