Triple
T1188787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annex 5 Discharges from Vessels |
E25308
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Annex of an international environmental agreement |
C7340
|
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: Annex of an international environmental agreement Context triple: [Annex 5 Discharges from Vessels, instanceOf, Annex of an international environmental agreement]
-
A.
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.
-
B.
chapter of an international treaty
A chapter of an international treaty is a major structural division that groups together related articles and provisions addressing a specific thematic area or subject matter within the overall agreement.
-
C.
international agreement implementation area
The international agreement implementation area is a defined domain—such as a sector, region, or policy field—within which the provisions of an international agreement are applied, monitored, and enforced.
-
D.
international agreement
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.
environmental cleanup agreement
An environmental cleanup agreement is a legally binding contract in which parties define responsibilities, standards, timelines, and cost allocations for investigating, remediating, and monitoring contamination at a specific site.
- F. None of above. chosen
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_69a49427d98881908646d6c63b8cea1e |
completed | March 1, 2026, 7:31 p.m. |
Created at: March 1, 2026, 7:45 p.m.