Triple
T35872000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSCE Mission to Croatia |
E1037247
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | post-conflict field operation |
C48880
|
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: post-conflict field operation Context triple: [OSCE Mission to Croatia, instanceOf, post-conflict field operation]
-
A.
peacekeeping area of operations
A peacekeeping area of operations is the geographically defined space within which peacekeeping forces are authorized and tasked to conduct missions, maintain security, and support the implementation of peace agreements.
-
B.
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.
-
C.
multidimensional peace operation
chosen
A multidimensional peace operation is a complex, integrated mission that combines military, police, and civilian components to support peace processes, protect civilians, and help build or restore legitimate and effective governance and institutions in post-conflict settings.
-
D.
conflict-affected area
A conflict-affected area is a geographic region where ongoing or recent armed violence, political instability, or social unrest significantly disrupts normal life, governance, and access to essential services.
-
E.
peace operations leadership structure
The peace operations leadership structure is the organized hierarchy of civilian, military, and police leaders responsible for planning, directing, coordinating, and overseeing all aspects of a peace operation to achieve its mandate.
- 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_69f76e1e701c8190a4990d4978ce4fe6 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.