Triple
T16343020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rambouillet Agreement |
E396855
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | proposed peace agreement |
C10715
|
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: proposed peace agreement Context triple: [Rambouillet Agreement, instanceOf, proposed peace agreement]
-
A.
peace proposal
chosen
A peace proposal is a formal plan or set of terms presented to conflicting parties with the aim of resolving disputes and establishing lasting harmony.
-
B.
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.
-
C.
peace negotiation
A peace negotiation is a structured process in which conflicting parties communicate and bargain to reach mutually acceptable agreements that end or reduce violence and establish conditions for lasting peace.
-
D.
peace clause
A peace clause is a contractual or legal provision in which parties agree to refrain from certain actions or disputes for a specified period, typically to maintain stability or allow negotiations.
-
E.
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.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:07 a.m.