Triple
T28957129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NPT 2010 Review Conference Final Document |
E731193
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United Nations conference 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 conference document Context triple: [NPT 2010 Review Conference Final Document, instanceOf, United Nations conference 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–sponsored conference
A United Nations–sponsored conference is a formally organized international meeting convened or supported by the UN to address global issues, negotiate agreements, and coordinate actions among member states and stakeholders.
-
D.
United Nations document series
A United Nations document series is a categorized collection of official UN documents grouped under a common symbol or theme to organize and track related records over time.
-
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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 8:48 a.m.