Triple
T14904578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Host Country Agreement between OPCW and the Netherlands |
E360095
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | host country agreement |
C823
|
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: host country agreement Context triple: [Host Country Agreement between OPCW and the Netherlands, instanceOf, host country agreement]
-
A.
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.
-
B.
headquarters agreement
chosen
A headquarters agreement is a formal treaty or contract between an international organization and a host state that defines the legal status, privileges, immunities, and operational conditions of the organization’s headquarters within that state.
-
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.
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.
-
E.
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.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 2:12 a.m.