Triple
T1304416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OAS General Assembly resolutions |
E27841
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international organization resolution |
C2011
|
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 organization resolution Context triple: [OAS General Assembly resolutions, instanceOf, international organization resolution]
-
A.
United Nations resolution
A United Nations resolution is a formal text adopted by a UN organ that expresses decisions, recommendations, or positions on international issues, guiding member states’ actions and the organization’s activities.
-
B.
international political declaration
chosen
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.
-
C.
international organization
An international organization is an institutional entity formed by multiple countries or global actors to coordinate policies, manage shared interests, and address transnational issues through cooperative frameworks and agreements.
-
D.
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.
-
E.
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.
- 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_69a496d7d83481908f83085854e51328 |
completed | March 1, 2026, 7:43 p.m. |
Created at: March 1, 2026, 7:51 p.m.