Triple
T9498051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resolution RC/Res.5 |
E229060
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | decision of an international conference |
C23719
|
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: decision of an international conference Context triple: [Resolution RC/Res.5, instanceOf, decision of an international conference]
-
A.
diplomatic conference
A diplomatic conference is a formal gathering of representatives from different states or international organizations convened to negotiate agreements, resolve disputes, or discuss issues of mutual concern.
-
B.
United Nations outcome document
chosen
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.
-
C.
international political declaration
An international political declaration is a formal, non-binding statement adopted by states or international bodies that articulates shared political intentions, principles, or commitments on global or regional issues.
-
D.
Council decision
A Council decision is a formal, binding resolution adopted by a council body that determines a course of action, policy, or outcome on matters within its authority.
-
E.
world congress
A world congress is a large international gathering of representatives, experts, or delegates from multiple countries convened to discuss, coordinate, and make decisions on global issues within a specific field or across various domains.
- 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_69ca84753660819098e8d416e89e26ae |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 7:56 p.m.