Triple
T28409203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doha Declaration on Financing for Development |
E719619
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United Nations consensus document |
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: United Nations consensus document Context triple: [Doha Declaration on Financing for Development, instanceOf, United Nations consensus document]
-
A.
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.
-
B.
United Nations report
A United Nations report is an official document produced by UN bodies that presents analysis, findings, and recommendations on international issues such as peace, development, human rights, and the environment.
-
C.
United Nations regulation
A United Nations regulation is a formal rule or standard adopted by UN bodies that guides or constrains the behavior of member states and international actors in specific policy areas to promote global cooperation, peace, and development.
-
D.
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.
-
E.
United Nations proposal
A United Nations proposal is a formal document submitted by member states or UN bodies that outlines recommended actions, policies, or resolutions for consideration, negotiation, and potential adoption by UN organs.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1:25 a.m.