Triple
T30989460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Ula Declaration |
E789625
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Gulf Cooperation Council agreement |
C57378
|
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: Gulf Cooperation Council agreement Context triple: [Al-Ula Declaration, instanceOf, Gulf Cooperation Council agreement]
-
A.
organ of the Gulf Cooperation Council
An organ of the Gulf Cooperation Council is an official institutional body established by the GCC to perform specific functions such as decision-making, coordination, implementation, or advisory roles in support of regional cooperation among member states.
-
B.
Sudanese political agreement
A Sudanese political agreement is a formal accord between Sudanese political actors or factions that outlines shared principles, power arrangements, and mechanisms for governance, conflict resolution, or transition.
-
C.
founding document of the Arab League
The founding document of the Arab League is the formal treaty that established the organization’s principles, structure, and objectives for cooperation among its member Arab states.
-
D.
bilateral military agreement
A bilateral military agreement is a formal pact between two states that outlines mutual defense commitments, security cooperation, and related military obligations and activities.
-
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. chosen
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_69f224c550b081909ddfceb0c3d03bdd |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:56 p.m.