Triple

T10507966
Position Surface form Disambiguated ID Type / Status
Subject London Amendment E247833 entity
Predicate instanceOf P0 FINISHED
Object environmental treaty amendment 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: environmental treaty amendment
Context triple: [London Amendment, instanceOf, environmental treaty amendment]
  • A. 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.
  • B. 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.
  • C. Annex of an international environmental agreement
    An annex of an international environmental agreement is a formally attached, legally significant document that provides detailed technical, scientific, procedural, or country-specific provisions that supplement and operationalize the main treaty text.
  • D. Annex of international environmental agreement
    An annex of an international environmental agreement is a supplementary, legally relevant document attached to the main treaty text that provides detailed technical, scientific, procedural, or implementation provisions which can often be updated more easily than the core agreement.
  • E. 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.
  • 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_69d381c4aa948190942e1d803143fb0e completed April 6, 2026, 9:49 a.m.
Created at: April 6, 2026, 12:26 p.m.