Triple
T19821871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paris Agreement rulebook |
E476214
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | UNFCCC decision text |
C42662
|
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: UNFCCC decision text Context triple: [Paris Agreement rulebook, instanceOf, UNFCCC decision text]
-
A.
UNFCCC decision package
An UNFCCC decision package is a negotiated set of interrelated decisions, texts, and commitments adopted together under the UN climate regime to advance collective action on climate change.
-
B.
conference of the parties
A conference of the parties is a formal meeting of all member states to a multilateral agreement, convened to review implementation, negotiate commitments, and make collective decisions under that agreement.
-
C.
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.
-
D.
United Nations climate mechanism
A United Nations climate mechanism is an institutional framework, process, or instrument established under the UN system to coordinate, implement, and monitor international efforts to mitigate and adapt to climate change.
-
E.
Kyoto Protocol flexibility mechanism
The Kyoto Protocol flexibility mechanism is a set of market-based tools—emissions trading, Joint Implementation, and the Clean Development Mechanism—that allow countries to meet their greenhouse gas reduction commitments cost-effectively by trading or financing emission reductions across borders.
- 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:50 p.m.