Triple
T29467244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Assembly of the States Parties to the 2003 Convention |
E747412
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organ of a treaty |
C34783
|
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: organ of a treaty Context triple: [General Assembly of the States Parties to the 2003 Convention, instanceOf, organ of a treaty]
-
A.
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.
-
B.
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.
-
C.
organ of international organization
chosen
An organ of an international organization is a structured body or component, such as an assembly, council, or secretariat, that performs specific functions and exercises powers on behalf of the organization under its founding charter or 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.
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.
- 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_69f0bd42cf308190bb01b20bc5b7c2d0 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 28, 2026, 3:54 p.m.