Triple
T7543634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridei mac Bili |
E178340
|
entity |
| Predicate | resultOfBattleOfDunNechtain |
P19109
|
FINISHED |
| Object | decisive Pictish victory |
—
|
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: decisive Pictish victory | Statement: [Bridei mac Bili, resultOfBattleOfDunNechtain, decisive Pictish victory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfBattleOfDunNechtain Context triple: [Bridei mac Bili, resultOfBattleOfDunNechtain, decisive Pictish victory]
-
A.
resultOfBattle
chosen
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
-
B.
battleWasPartOf
Indicates that a specific battle occurred as a component or phase within a larger military campaign, war, or conflict.
-
C.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
D.
battleOccurredNear
Indicates that a battle took place in spatial proximity to a specified location or entity.
-
E.
battleAlsoKnownAs
Indicates that a particular battle is known by an alternative name or names.
- 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_69c69f2be3888190a6667a27f8f195e9 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f896a27481908b2e120208f268e7 |
completed | March 27, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69c6f4daad6c8190af2b8ae88d2c8cb7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:48 p.m.