Triple
T37653646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johannesburg Declaration on Sustainable Development |
E937238
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | outcome document of a UN summit |
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: outcome document of a UN summit Context triple: [Johannesburg Declaration on Sustainable Development, instanceOf, outcome document of a UN summit]
-
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 high-level meeting
A United Nations high-level meeting is a formal gathering of heads of state, government leaders, and senior officials convened under the UN framework to address and coordinate action on critical global issues.
-
C.
world summit
A world summit is a high-level international conference where leaders from multiple countries convene to discuss and coordinate responses to global issues and policies.
-
D.
summit side event
A summit side event is an auxiliary gathering or session held alongside a main summit to explore specific topics, foster networking, or highlight complementary initiatives without being part of the core agenda.
-
E.
article of United Nations General Assembly resolution
An article of a United Nations General Assembly resolution is a distinct, numbered provision within the resolution text that sets out specific decisions, principles, or actions agreed upon by the Assembly.
- 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.