Triple
T20677086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations General Assembly Resolution 2758 |
E508186
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | diplomatic recognition decision |
C32214
|
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: diplomatic recognition decision Context triple: [United Nations General Assembly Resolution 2758, instanceOf, diplomatic recognition decision]
-
A.
diplomatic declaration
A diplomatic declaration is a formal, often public statement issued by a state or group of states to articulate positions, intentions, or commitments in international relations.
-
B.
diplomatic position
A diplomatic position is an official role within a government or international organization responsible for managing and representing a state's or entity's interests in foreign relations and negotiations.
-
C.
diplomatic relations
Diplomatic relations are the formal and informal interactions and agreements between sovereign states or international actors aimed at managing conflicts, fostering cooperation, and advancing mutual interests through negotiation and representation.
-
D.
diplomatic policy
Diplomatic policy is a strategic framework guiding a state’s interactions and negotiations with other international actors to advance its political, economic, and security interests while managing conflicts and alliances.
-
E.
international political decision
chosen
An international political decision is a formal choice or policy action made by one or more states or global governing bodies that shapes relations, obligations, or power dynamics across national borders.
- 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_69e0b4c1164881909a3bf1e3ddb2bc32 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:44 a.m.