Triple
T23860825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annex 10 – Civilian Implementation Framework |
E592443
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international peace agreement instrument |
C19675
|
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: international peace agreement instrument Context triple: [Annex 10 – Civilian Implementation Framework, instanceOf, international peace agreement instrument]
-
A.
international agreement
An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
-
B.
peace and security instrument
chosen
A peace and security instrument is a formal mechanism, tool, or framework—such as a treaty, policy, program, or operational measure—designed to prevent conflict, reduce violence, and protect individuals and communities from threats to their safety and stability.
-
C.
private international law instrument
A private international law instrument is a legal tool—such as a treaty, regulation, or convention—that coordinates which jurisdiction’s laws and courts apply to cross-border private disputes and how foreign judgments are recognized and enforced.
-
D.
peace settlement
A peace settlement is a formal agreement between conflicting parties that ends hostilities and establishes terms for lasting resolution and post-conflict relations.
-
E.
peace ordinance
A peace ordinance is a local law or regulation enacted by a governing body to prevent disturbances, maintain public order, and promote peaceful coexistence within a community.
- 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_69e25d22eb488190914b193aff952e83 |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 8:12 p.m.