Triple
T6972662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAARC Action Plan on Culture |
E161634
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intergovernmental action plan |
C20610
|
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: intergovernmental action plan Context triple: [SAARC Action Plan on Culture, instanceOf, intergovernmental action plan]
-
A.
intergovernmental programme
An intergovernmental programme is a coordinated set of policies, activities, or initiatives jointly designed, funded, and implemented by multiple governments or international organizations to address shared issues or achieve common goals across borders.
-
B.
intergovernmental platform
An intergovernmental platform is a structured forum or mechanism through which multiple governments collaborate, coordinate policies, share information, and make joint decisions on issues of common interest.
-
C.
international initiative
An international initiative is a coordinated effort among multiple countries or global organizations aimed at addressing shared challenges or achieving common goals across national borders.
-
D.
intergovernmental working group framework
An intergovernmental working group framework is a structured, collaborative arrangement through which multiple governments coordinate, negotiate, and develop joint policies, standards, or actions on shared issues.
-
E.
global action plan
A global action plan is a coordinated, strategic framework that outlines shared goals, responsibilities, timelines, and resources for addressing worldwide challenges across nations and organizations.
- 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_69c68854a0d88190bc0bf82263f1afce |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:30 p.m.