Triple
T20564604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Post-Cotonou Agreement |
E504934
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | treaty between the European Union and ACP states |
C566
|
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: treaty between the European Union and ACP states Context triple: [Post-Cotonou Agreement, instanceOf, treaty between the European Union and ACP states]
-
A.
European Union convention
A European Union convention is a formal international agreement between EU member states, or between the EU and other parties, that establishes common rules, standards, or cooperation frameworks in specific policy areas.
-
B.
treaty
chosen
A treaty is a formal, legally binding agreement between two or more sovereign states or international entities that defines their mutual rights, obligations, and commitments.
-
C.
international agreement
An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
-
D.
treaty-based alliance
A treaty-based alliance is a formal agreement between two or more sovereign entities that legally binds them to cooperate on specified political, military, economic, or other mutual interests under defined terms and obligations.
-
E.
act of the Lisbon Agreement
An act of the Lisbon Agreement is a formal revision or amendment instrument adopted by member states that updates, supplements, or replaces provisions of the original Lisbon Agreement on the protection of appellations of origin and their international registration.
- 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.