Triple
T31979602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | የኢትዮጵያ ንጉሳዊ መከላከያ ሠራዊት |
E816540
|
entity |
| Predicate | contributedUnit |
P31806
|
FINISHED |
| Object | Kagnew Battalion |
—
|
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: Kagnew Battalion | Statement: [የኢትዮጵያ ንጉሳዊ መከላከያ ሠራዊት, contributedUnit, Kagnew Battalion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contributedUnit Context triple: [የኢትዮጵያ ንጉሳዊ መከላከያ ሠራዊት, contributedUnit, Kagnew Battalion]
-
A.
componentUnit
Indicates that one entity functions as a constituent or sub-unit that forms part of a larger composite entity.
-
B.
supportedUnit
chosen
Indicates that one entity provides assistance, resources, or backing to another entity functioning as a unit or sub-organization.
-
C.
associatedUnitType
Indicates that one entity is linked to or characterized by a particular type or category of unit.
-
D.
introducedByUnit
Indicates that something was brought into existence, initiated, or caused as a result of the actions or influence of a particular unit.
-
E.
commissionedUnit
Indicates that one entity formally authorizes or assigns another entity (the commissioned unit) to carry out a specific task, role, or function.
- 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: May 1, 2026, 12:11 a.m.