Triple
T31767119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NRM |
E810839
|
entity |
| Predicate | promotesPolicy |
P1086
|
FINISHED |
| Object | stability and security in Uganda |
—
|
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: stability and security in Uganda | Statement: [NRM, promotesPolicy, stability and security in Uganda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotesPolicy Context triple: [NRM, promotesPolicy, stability and security in Uganda]
-
A.
promotes
Indicates that one entity actively supports, advances, or encourages the growth, adoption, or success of another entity or outcome.
-
B.
recommendedPolicy
Indicates that one entity suggests or endorses a particular policy for another entity or situation.
-
C.
advancesPolicyOf
Indicates that one entity actively promotes, supports, or furthers the policy objectives or agenda of another entity.
-
D.
supportsPolicy
chosen
Indicates that one entity endorses, backs, or is in favor of a particular policy or set of policies.
-
E.
establishedPolicy
Indicates that a policy has been formally created, adopted, and put into effect as a guiding rule or standard.
- 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_69f348e463e08190b902d4819195e1f0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 30, 2026, 11:32 p.m.