Triple
T9803429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNSMIL |
E237895
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special political mission |
C23004
|
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: special political mission Context triple: [UNSMIL, instanceOf, special political mission]
-
A.
United Nations special political mission
chosen
A United Nations special political mission is a field-based UN presence, established by the Security Council or General Assembly, mandated to support peace processes, political transitions, conflict prevention, or post-conflict stabilization through diplomacy, mediation, and related political activities.
-
B.
military mission
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.
-
C.
international mission
An international mission is a coordinated effort by multiple countries or global organizations to achieve a shared objective—such as humanitarian aid, peacekeeping, scientific research, or development—across national borders.
-
D.
rescue mission
A rescue mission is a coordinated operation undertaken to locate, assist, and safely extract individuals or groups from dangerous or life-threatening situations.
-
E.
public service mission
A public service mission is a guiding purpose or mandate focused on delivering benefits, support, or protections to the public or a specific community, typically through government or nonprofit actions that prioritize the common good over private gain.
- 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_69ca84dd4608819097ff4ed00feca280 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:29 p.m.