Triple
T21200307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfredian–Viking wars |
E522436
|
entity |
| Predicate | commander |
P1061
|
FINISHED |
| Object | Guthrum |
—
|
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: Guthrum | Statement: [Alfredian–Viking wars, commander, Guthrum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Guthrum Context triple: [Alfredian–Viking wars, commander, Guthrum]
-
A.
Guthrum
chosen
Guthrum was a 9th-century Danish Viking leader and king of the Danelaw, best known for his conflicts with Alfred the Great and his eventual conversion to Christianity.
-
B.
Guthred of Kent
Guthred of Kent was an early medieval monarch who ruled the Anglo-Saxon Kingdom of Kent in what is now southeastern England.
-
C.
Sigeric
Sigeric was a short-lived early 5th-century Visigothic king known for briefly succeeding Alaric I before being replaced by Wallia.
-
D.
Sigeric
Sigeric was a Burgundian prince of the early 6th century, known primarily as the son and short-lived heir of King Sigismund of Burgundy.
-
E.
Oesbern
Oesbern is a suburban district of the town of Menden in North Rhine-Westphalia, Germany.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b5112d8881909510b2dcdc93106d |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73430c5a08190aeb6a62eec0f43a3 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 3:18 p.m.