Triple
T20564603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Post-Cotonou Agreement |
E504934
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | partnership framework |
C39723
|
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: partnership framework Context triple: [Post-Cotonou Agreement, instanceOf, partnership framework]
-
A.
partnership agreement
A partnership agreement is a legally binding contract between two or more parties that defines their business relationship, including ownership shares, roles, responsibilities, profit and loss distribution, and procedures for decision-making and dispute resolution.
-
B.
partnership mechanism
A partnership mechanism is a structured approach, process, or set of rules that governs how two or more parties collaborate, share resources, distribute responsibilities, and allocate benefits to achieve common objectives.
-
C.
partnership structure
A partnership structure is an organizational arrangement in which two or more parties share ownership, responsibilities, risks, and profits according to agreed-upon terms.
-
D.
strategic partnership
A strategic partnership is a long-term, collaborative relationship between two or more independent organizations that align resources, capabilities, and objectives to achieve mutually beneficial competitive advantages they could not easily attain alone.
-
E.
foundational framework agreement
chosen
A foundational framework agreement is a high-level, overarching contract that establishes the core principles, structures, and long-term terms under which more detailed or specific agreements will be developed and executed.
- 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_69e0b4b6587c8190aee63dc7cff244ea |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:39 a.m.