Triple
T15739130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Budapest Summit decisions |
E381555
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | summit outcome document |
C23989
|
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: summit outcome document Context triple: [Budapest Summit decisions, instanceOf, summit outcome document]
-
A.
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.
-
B.
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.
-
C.
concluding document
chosen
A concluding document is a final written record that summarizes outcomes, decisions, and next steps at the end of a process, project, or agreement.
-
D.
OSCE document corpus
A structured collection of documents related to Objective Structured Clinical Examinations (OSCE), including station checklists, scoring rubrics, case scenarios, and examiner guidelines, organized for reference, analysis, and educational use.
-
E.
international political declaration
An international political declaration is a formal, non-binding statement adopted by states or international bodies that articulates shared political intentions, principles, or commitments on global or regional issues.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:46 a.m.