Triple
T29901371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Depositary Notifications (CN series) |
E759415
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United Nations treaty depositary communication |
C56406
|
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: United Nations treaty depositary communication Context triple: [Depositary Notifications (CN series), instanceOf, United Nations treaty depositary communication]
-
A.
United Nations outcome document
A United Nations outcome document is a formal, negotiated text adopted by UN member states that records agreed conclusions, commitments, and recommended actions resulting from a UN conference, summit, or meeting.
-
B.
United Nations protocol
United Nations protocol is the formal set of rules, procedures, and diplomatic customs that govern conduct, precedence, ceremonies, and official interactions within and around the United Nations.
-
C.
diplomatic declaration
A diplomatic declaration is a formal, often public statement issued by a state or group of states to articulate positions, intentions, or commitments in international relations.
-
D.
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.
-
E.
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.
- F. None of above. chosen
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_69f224600590819085e148a01c056ef6 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:06 p.m.