Triple
T1591619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resolute Support Mission |
E34189
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | NATO mission |
C5823
|
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: NATO mission Context triple: [Resolute Support Mission, instanceOf, NATO mission]
-
A.
NATO military position
A NATO military position is a standardized role or appointment within the North Atlantic Treaty Organization’s integrated command or force structure, defining specific responsibilities, rank equivalencies, and functions across member nations’ armed forces.
-
B.
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.
-
C.
military mission
chosen
A military mission is a coordinated operation undertaken by armed forces to achieve specific strategic, operational, or tactical objectives within defined constraints and rules of engagement.
-
D.
military operation
A military operation is a coordinated and planned set of actions conducted by armed forces to achieve specific strategic, operational, or tactical objectives.
-
E.
multinational mission mechanism
A multinational mission mechanism is a structured framework of processes, agreements, and coordinating bodies that enables multiple countries or organizations to collaboratively plan, resource, and execute a shared mission across borders.
- F. None of above.
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_69a885fceb2c8190b47e0f7c0aefbff0 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:27 p.m.