Triple
T31767105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NRM |
E810839
|
entity |
| Predicate | hasSuccessorMilitary |
P121397
|
FINISHED |
| Object | Uganda People’s Defence Force |
—
|
NE NERFINISHED |
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: Uganda People’s Defence Force | Statement: [NRM, hasSuccessorMilitary, Uganda People’s Defence Force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuccessorMilitary Context triple: [NRM, hasSuccessorMilitary, Uganda People’s Defence Force]
-
A.
hasSuccession
Indicates that one entity follows or replaces another in a sequence, order, or position, forming a succession relationship between them.
-
B.
hadMilitaryFollowing
Indicates that an entity was supported or backed by a group of military personnel or forces.
-
C.
successorInU.S.Service
Indicates that one entity directly follows another in holding a particular position or role within U.S. service.
-
D.
hasSuccessorRegime
Indicates that one regime follows and replaces another as its direct successor in a sequence of governing authorities.
-
E.
notableSuccessorUnit
chosen
Indicates that one unit is recognized as a particularly significant or prominent successor to another unit in a sequence or lineage.
- 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_69fecb4d02f881909a9ee97ce98000d5 |
completed | May 9, 2026, 5:51 a.m. |
| PD | Predicate disambiguation | batch_69fec9846c1c8190b317f0711f0755db |
completed | May 9, 2026, 5:43 a.m. |
Created at: April 30, 2026, 11:32 p.m.