Triple
T20599378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lomé Convention |
E506133
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | treaty between the European Community and ACP states |
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: treaty between the European Community and ACP states Context triple: [Lomé Convention, instanceOf, treaty between the European Community and ACP states]
-
A.
treaty
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.
-
B.
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.
-
C.
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.
-
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.
regional economic integration protocol
A regional economic integration protocol is a formal agreement among neighboring or closely linked countries that coordinates trade, investment, and regulatory policies to reduce barriers and promote a more unified regional market.
- 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.