Triple
T29585398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ethiopians |
E753704
|
entity |
| Predicate | majorBattleVictory |
P4779
|
FINISHED |
| Object | Battle of Adwa (1896) |
—
|
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: Battle of Adwa (1896) | Statement: [Ethiopians, majorBattleVictory, Battle of Adwa (1896)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorBattleVictory Context triple: [Ethiopians, majorBattleVictory, Battle of Adwa (1896)]
-
A.
largerForceDefeated
Indicates that in a conflict or contest, the side with the numerically or materially larger force was ultimately defeated by its opponent.
-
B.
resultOfMilitaryCampaign
Indicates that one event, condition, or outcome occurs as a direct consequence of a specified military campaign.
-
C.
yearOfMajorVictory
Indicates the specific year in which a major victory associated with the subject occurred.
-
D.
victoryIn
chosen
Indicates that one entity achieves a win or success in a specific contest, event, or competitive context involving another entity.
-
E.
strategicEffectOfVictory
Indicates that a victory produces a broader strategic impact or consequence beyond the immediate outcome of the conflict or contest.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: April 28, 2026, 6:10 p.m.