Triple
T1619758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northumbria |
E35002
|
entity |
| Predicate | sufferedVikingRaid |
P21625
|
FINISHED |
| Object | Lindisfarne 793 |
—
|
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: Lindisfarne 793 | Statement: [Northumbria, sufferedVikingRaid, Lindisfarne 793]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sufferedVikingRaid Context triple: [Northumbria, sufferedVikingRaid, Lindisfarne 793]
-
A.
attackedIn
Indicates that one entity carried out an attack in the location, context, or time frame specified by another entity or value.
-
B.
wasInvadedBy
chosen
Indicates that a place or territory was subjected to an incursion or attack carried out by another entity or group.
-
C.
damagedBy
Indicates that one entity has caused harm, impairment, or deterioration to another entity.
-
D.
fellOn
Indicates that one entity moved downward, typically due to gravity, and came to rest on the surface of another entity.
-
E.
warDamage
Indicates damage that was caused as a direct consequence of war or armed conflict.
- 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_69a886023194819080a3fccd6e325d0e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf4a0ef748190ae52b9656474c0ef |
completed | March 6, 2026, 3:37 p.m. |
| PD | Predicate disambiguation | batch_69a907c731808190a1d998155041b3c1 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.