Triple
T34446578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Programme of Action for Youth |
E884243
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international action plan |
C16202
|
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 action plan Context triple: [World Programme of Action for Youth, instanceOf, international action plan]
-
A.
intergovernmental action plan
An intergovernmental action plan is a coordinated framework of policies, objectives, and implementation steps jointly developed and agreed upon by multiple governments to address shared issues or goals across jurisdictions.
-
B.
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.
-
C.
global action plan
chosen
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.
-
D.
international framework
An international framework is a structured set of principles, rules, and mechanisms agreed upon by multiple countries to guide cooperation, coordination, and decision-making on shared global issues.
-
E.
international policy instrument
An international policy instrument is a formal agreement, framework, or mechanism used by multiple countries or international organizations to coordinate actions, set standards, or achieve shared policy objectives across 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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2 a.m.