Triple
T14720377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paris Protocol |
E345796
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | annex to peace accords |
C7339
|
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: annex to peace accords Context triple: [Paris Protocol, instanceOf, annex to peace accords]
-
A.
component of peace accords
A component of peace accords is a distinct provision or mechanism within a negotiated agreement that addresses specific issues—such as security, governance, justice, or reconstruction—to facilitate the resolution of conflict and the establishment of sustainable peace.
-
B.
treaty annex
A treaty annex is a supplementary document attached to a main treaty that provides detailed provisions, technical specifications, or additional terms that form an integral part of the overall agreement.
-
C.
annex to international agreement
chosen
An annex to an international agreement is a supplementary document formally attached to the main treaty that provides detailed provisions, technical specifications, or additional obligations that are integral to and legally binding under the agreement.
-
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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:29 a.m.