Triple
T35511689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Direnni Hegemony |
E1026298
|
entity |
| Predicate | resultOfBattleOfGlenumbraMoors |
P19109
|
FINISHED |
| Object | defeat of Alessian army |
—
|
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: defeat of Alessian army | Statement: [Direnni Hegemony, resultOfBattleOfGlenumbraMoors, defeat of Alessian army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfBattleOfGlenumbraMoors Context triple: [Direnni Hegemony, resultOfBattleOfGlenumbraMoors, defeat of Alessian army]
-
A.
resultOfBattle
chosen
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
-
B.
Battle of Halen
Indicates a military engagement or conflict that took place at or around the location known as Halen.
-
C.
resultOfSiege
Indicates that one entity is the outcome or consequence produced by a siege conducted against another entity.
-
D.
resultOfMilitaryCampaign
Indicates that one event, condition, or outcome occurs as a direct consequence of a specified military campaign.
-
E.
sideInBattleOfCarbisdale
Indicates being a participating side or faction in the Battle of Carbisdale.
- 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: May 3, 2026, 4:04 p.m.