Triple
T13438462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Control Commission |
E320291
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ceasefire supervision commission |
C5969
|
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: ceasefire supervision commission Context triple: [International Control Commission, instanceOf, ceasefire supervision commission]
-
A.
ceasefire
A ceasefire is a mutually agreed temporary suspension of active hostilities between conflicting parties, typically intended to create conditions for negotiation or humanitarian relief.
-
B.
peace commission
A peace commission is an official body established to investigate conflicts, promote dialogue, and recommend measures to prevent, resolve, or reconcile disputes between parties.
-
C.
armistice supervision body
chosen
An armistice supervision body is an organization established to monitor, verify, and enforce compliance with the terms of a ceasefire or armistice agreement between conflicting parties.
-
D.
conciliation commission
A conciliation commission is a temporary, impartial body established—often under international or contractual agreements—to investigate a dispute and propose nonbinding solutions aimed at amicable settlement between the parties.
-
E.
OSCE field mission
An OSCE field mission is a temporary or long-term presence deployed by the Organization for Security and Co-operation in Europe to support participating States in conflict prevention, crisis management, and post-conflict rehabilitation through monitoring, advising, and capacity-building activities.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:40 p.m.