Triple
T21812636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plurilateral Agreement on Government Procurement |
E538515
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | plurilateral 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: plurilateral agreement Context triple: [Plurilateral Agreement on Government Procurement, instanceOf, plurilateral agreement]
-
A.
preferential trade agreement
A preferential trade agreement is an arrangement between two or more countries to reduce tariffs and other trade barriers on certain products or services for member nations, granting them more favorable access than non-members.
-
B.
bilateral diplomatic agreement
A bilateral diplomatic agreement is a formal, negotiated arrangement between two sovereign states that defines mutual rights, obligations, and cooperative actions in specific areas of shared interest.
-
C.
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.
-
D.
bilateral trade association
A bilateral trade association is an organization formed between two countries to promote, facilitate, and regulate trade and economic cooperation through agreements, advocacy, and joint initiatives.
-
E.
annex to international agreement
An annex to an international agreement is a supplementary document formally attached to the main treaty that provides detailed provisions, technical specifications, or additional obligations that are integral to and legally binding under the agreement.
- 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:53 p.m.