Triple
T2681247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basket II |
E56577
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | section of an international agreement |
C544
|
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: section of an international agreement Context triple: [Basket II, instanceOf, section of an international agreement]
-
A.
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.
-
B.
article of an international treaty
chosen
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.
-
C.
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.
-
D.
party to an international treaty
A party to an international treaty is a state or international organization that has formally consented to be bound by the treaty’s terms in accordance with international law.
-
E.
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.
- 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_69ab4a4b13fc81909dfdb3f23da46832 |
completed | March 6, 2026, 9:42 p.m. |
Created at: March 6, 2026, 9:54 p.m.