Triple
T29711704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uganda Military Academy Kabamba |
E751798
|
entity |
| Predicate | armedForcesServed |
P35775
|
FINISHED |
| Object | Uganda Peoples' Defence Forces |
—
|
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 Peoples' Defence Forces | Statement: [Uganda Military Academy Kabamba, armedForcesServed, Uganda Peoples' Defence Forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armedForcesServed Context triple: [Uganda Military Academy Kabamba, armedForcesServed, Uganda Peoples' Defence Forces]
-
A.
hadMilitaryServiceFrom
Indicates that an entity performed or was engaged in military service starting from a specified point in time.
-
B.
placeOfMilitaryService
chosen
Indicates the location or institution where a person performed their military service.
-
C.
involvesMilitaryService
Indicates that the relationship or situation includes participation in, obligation to, or association with formal military service.
-
D.
militaryUnitTypeServed
Indicates that an entity served in, or was a member of, a specific type of military unit.
-
E.
stanceOnMilitaryService
Indicates an entity’s expressed position, attitude, or policy regarding military service.
- 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_69f0d62748848190b030d0a703629a7d |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672d911248190af67e09e0886b46d |
completed | May 2, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:31 p.m.