Triple
T282913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations General Assembly Resolution 67/19 |
E5827
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international diplomatic document |
C2056
|
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: international diplomatic document Context triple: [United Nations General Assembly Resolution 67/19, instanceOf, international diplomatic document]
-
A.
international agreement
An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
-
B.
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.
-
C.
diplomatic conference
A diplomatic conference is a formal gathering of representatives from different states or international organizations convened to negotiate agreements, resolve disputes, or discuss issues of mutual concern.
-
D.
international relations
International relations is the study and practice of how states and other global actors interact, cooperate, and conflict within the international system.
-
E.
intergovernmental organization
An intergovernmental organization is a formal entity created by sovereign states through treaties or agreements to cooperate on common interests, coordinate policies, and address international issues.
- F. None of above. chosen
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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.