Triple
T6990137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Africa We Want |
E162063
|
entity |
| Predicate | goalFramework |
P52034
|
FINISHED |
| Object | seven aspirations of Agenda 2063 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: seven aspirations of Agenda 2063 | Statement: [The Africa We Want, goalFramework, seven aspirations of Agenda 2063]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalFramework Context triple: [The Africa We Want, goalFramework, seven aspirations of Agenda 2063]
-
A.
goalStructure
chosen
Indicates the overarching objective or intended outcome that organizes and guides the structure of related actions, components, or relationships.
-
B.
strategicGoal
Indicates that one entity represents a long-term objective or desired outcome that another entity is intentionally aiming to achieve or align actions toward.
-
C.
goalType
Indicates the specific category or nature of a goal associated with an entity or action.
-
D.
goals
Indicates that an entity has objectives, targets, or desired outcomes it aims to achieve.
-
E.
normativeGoal
Indicates that one entity is a desired or prescribed objective, standard, or end state that another entity ought to pursue or realize.
- F. None of above.
Provenance (3 batches)
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_69c68856d7808190ab33ee914640281b |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbc08758819083d36a1fc0463b27 |
completed | March 27, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c4a18881908d267137daed828b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:32 p.m.