Triple
T27903109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Winwaed |
E705688
|
entity |
| Predicate | impactOnNorthumbria |
P164290
|
FINISHED |
| Object | consolidation of Oswiu's rule |
—
|
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: consolidation of Oswiu's rule | Statement: [Battle of the Winwaed, impactOnNorthumbria, consolidation of Oswiu's rule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactOnNorthumbria Context triple: [Battle of the Winwaed, impactOnNorthumbria, consolidation of Oswiu's rule]
-
A.
impactOnScotland
Indicates the effect or consequences that something has specifically on Scotland.
-
B.
outcomeForNorthumbria
chosen
Indicates the result, consequence, or effect that an event, action, or situation has specifically on Northumbria.
-
C.
reignAsEarlOfNorthumbriaEnd
Indicates the point in time or event at which an individual's tenure or rule as Earl of Northumbria comes to an end.
-
D.
reignAsEarlOfNorthumbriaStart
Indicates the time at which a person begins their tenure ruling in the position of Earl of Northumbria.
-
E.
successorAsEarlOfNorthumbria
Indicates that one entity became the next Earl of Northumbria following another entity in succession.
- 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_69ef96b490ac8190a412d04c5d009f3e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 27, 2026, 6:43 p.m.