Triple
T20599377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lomé Convention |
E506133
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | development cooperation agreement |
C824
|
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: development cooperation agreement Context triple: [Lomé Convention, instanceOf, development cooperation agreement]
-
A.
development cooperation policy
Development cooperation policy is a strategic framework that guides how governments and organizations plan, coordinate, and implement international development assistance to promote sustainable economic, social, and environmental progress in partner countries.
-
B.
development cooperation agency
A development cooperation agency is an organization that plans, finances, and implements international programs and partnerships to support sustainable economic, social, and institutional development in partner countries.
-
C.
bilateral development agency
A bilateral development agency is a government-funded organization that provides financial, technical, and policy support directly from one country to another to promote economic and social development.
-
D.
international agreement
chosen
An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
-
E.
development assistance fund
A development assistance fund is a pooled financial resource dedicated to supporting projects and programs that promote economic, social, and institutional development, typically in low- and middle-income regions.
- 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_69e0b4ba6ae88190af871e1f9522c704 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:40 a.m.