Triple
T21802267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IOSCO Multilateral Memorandum of Understanding |
E538265
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multilateral memorandum of understanding |
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: multilateral memorandum of understanding Context triple: [IOSCO Multilateral Memorandum of Understanding, instanceOf, multilateral memorandum of understanding]
-
A.
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.
-
B.
bilateral military agreement
A bilateral military agreement is a formal pact between two states that outlines mutual defense commitments, security cooperation, and related military obligations and activities.
-
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.
intergovernmental consensus
Intergovernmental consensus is a collective agreement reached among multiple governments or states, typically through negotiation and compromise, that establishes a shared position or decision on a specific issue.
-
E.
multilateral development forum
A multilateral development forum is a structured platform where multiple countries and stakeholders convene to coordinate policies, share knowledge, and mobilize resources for sustainable economic and social development.
- 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_69e0c4733f4081909a86622e7e6d15d2 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:53 p.m.