Triple
T38262234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fourth Amendment of the Articles of Agreement of the International Monetary Fund |
E1017957
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | amendment to an international treaty |
C4085
|
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: amendment to an international treaty Context triple: [Fourth Amendment of the Articles of Agreement of the International Monetary Fund, instanceOf, amendment to an international treaty]
-
A.
amendments to international treaty
Amendments to international treaty: formal, negotiated changes or additions agreed upon by the treaty parties that modify, clarify, or expand the original treaty’s provisions and obligations.
-
B.
treaty amendment
chosen
A treaty amendment is a formal, negotiated change to an existing international agreement that modifies, adds to, or removes specific obligations or provisions for its parties.
-
C.
article of an international treaty
An article of an international treaty is a distinct, numbered provision that sets out specific rights, obligations, definitions, or procedures agreed upon by the treaty’s parties.
-
D.
amendment
An amendment is a formal change or addition made to a law, contract, constitution, or other official document to modify its original terms or provisions.
-
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_69f76de33e4481909099fa812709bd42 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.