Triple
T17541006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Protocol 2 concerning the application to works of certain international organizations |
E427197
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international treaty protocol |
C824
|
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: international treaty protocol Context triple: [Protocol 2 concerning the application to works of certain international organizations, instanceOf, international treaty protocol]
-
A.
international agreement
chosen
An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
-
B.
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.
-
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.
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.
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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:49 a.m.