Triple
T13475718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | state budget of Morocco |
E318243
|
entity |
| Predicate | policyObjectives |
P88042
|
FINISHED |
| Object | economic growth |
—
|
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: economic growth | Statement: [state budget of Morocco, policyObjectives, economic growth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policyObjectives Context triple: [state budget of Morocco, policyObjectives, economic growth]
-
A.
policyAim
chosen
Indicates that a policy is intended to achieve, promote, or be directed toward a particular goal or objective.
-
B.
nationalGoals
Indicates a relationship where certain objectives or targets are officially set or recognized as the goals of a nation.
-
C.
politicalGoal
Indicates a relationship where an entity aims to achieve, promote, or realize a specific political outcome, policy, or state of affairs.
-
D.
policyFocus
Indicates that an entity (such as a person, organization, or document) is primarily concerned with, directed toward, or centered on a particular policy area or issue.
-
E.
aimOf
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf2551b48190a074fd256791742d |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69dbadfddefc81909ef7fde23b181b5c |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.