Triple

T35087080
Position Surface form Disambiguated ID Type / Status
Subject Implementation Support Unit of the BWC E1012605 entity
Predicate instanceOf P0 FINISHED
Object treaty implementation support body C57113 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: treaty implementation support body
Context triple: [Implementation Support Unit of the BWC, instanceOf, treaty implementation support body]
  • A. subsidiary body of a treaty chosen
    A subsidiary body of a treaty is an institutional mechanism established under a treaty to perform specific functions—such as implementation, monitoring, negotiation, or technical support—on behalf of the treaty’s parties.
  • B. treaty implementation rules
    Treaty implementation rules are the detailed legal and administrative provisions that translate a treaty’s general obligations into specific, enforceable procedures and standards within a jurisdiction.
  • C. intergovernmental legal body
    An intergovernmental legal body is an organization formed by multiple governments to develop, interpret, or oversee the implementation of international legal norms, agreements, and dispute-resolution mechanisms.
  • D. treaty body resolution
    A treaty body resolution is a formal decision or recommendation adopted by an international treaty-monitoring body that interprets, applies, or guides implementation of the provisions of a specific treaty.
  • 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_69f76dd432ec8190969bc32acfc152b1 completed May 3, 2026, 3:46 p.m.
Created at: May 3, 2026, 4:01 p.m.