Triple
T2378687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boé Declaration on Regional Security |
E46260
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional security declaration |
C2011
|
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: regional security declaration Context triple: [Boé Declaration on Regional Security, instanceOf, regional security declaration]
-
A.
international political declaration
chosen
An international political declaration is a formal, non-binding statement adopted by states or international bodies that articulates shared political intentions, principles, or commitments on global or regional issues.
-
B.
diplomatic declaration
A diplomatic declaration is a formal, often public statement issued by a state or group of states to articulate positions, intentions, or commitments in international relations.
-
C.
trilateral security partners
Trilateral security partners are three sovereign entities that formally coordinate defense, intelligence, and strategic policies to enhance their collective security and regional or global stability.
-
D.
UNESCO declaration
A UNESCO declaration is a formal, non-binding instrument adopted by UNESCO’s governing bodies that sets out shared principles, standards, or commitments on cultural, educational, scientific, or ethical issues to guide member states and the international community.
-
E.
collective defense agreement
A collective defense agreement is a formal pact among multiple states committing each to consider an attack on one member as an attack on all and to respond with coordinated defense measures.
- 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_69a88a1554a48190a0180682bcf099be |
completed | March 4, 2026, 7:37 p.m. |
Created at: March 4, 2026, 7:57 p.m.