Triple
T28957128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NPT 2010 Review Conference Final Document |
E731193
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | consensus outcome 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: consensus outcome document Context triple: [NPT 2010 Review Conference Final Document, instanceOf, consensus outcome document]
-
A.
concluding document
A concluding document is a final written record that summarizes outcomes, decisions, and next steps at the end of a process, project, or agreement.
-
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.
consensus-based decision-making process
A consensus-based decision-making process is a collaborative method in which all participants work together to reach a mutually acceptable agreement that everyone can support or at least live with, rather than relying on majority rule.
-
D.
set of draft conclusions
A set of draft conclusions is a provisional collection of tentative, logically derived end statements that summarize current findings or reasoning, subject to further review and revision.
-
E.
post–Cold War settlement document
A post–Cold War settlement document is a formal agreement or framework, typically involving states and international organizations, that redefines political, security, and economic arrangements in the aftermath of the Cold War’s bipolar order.
- 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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 8:48 a.m.