Triple
T20524614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hrethel |
E503902
|
entity |
| Predicate | fatherOf |
P120
|
FINISHED |
| Object | Hygelac |
—
|
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: Hygelac | Statement: [Hrethel, fatherOf, Hygelac]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hygelac Context triple: [Hrethel, fatherOf, Hygelac]
-
A.
Hygelac
chosen
Hygelac is the legendary king of the Geats and uncle to the hero Beowulf in the Old English epic poem.
-
B.
Scylding
The Scyldings are a legendary royal dynasty of Danish rulers prominently featured in the Old English epic poem "Beowulf."
-
C.
Hrethel
Hrethel is a legendary king of the Geats in the Old English epic Beowulf, known as Beowulf’s foster-father and a central figure in the poem’s royal lineage.
-
D.
Hrothmund
Hrothmund is a legendary Danish prince from the Old English epic Beowulf, known as one of King Hrothgar’s sons and a member of the Scylding royal line.
-
E.
Hruodberht
Hruodberht is a historical personal name of Germanic origin, likely borne by early medieval European figures and appearing in sources with variant spellings such as Hruodperht.
- 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_69e0b4b3a6e08190ae663701f50fab8e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69f48691c8190af0ac959e92e10d9 |
completed | April 20, 2026, 9:48 p.m. |
Created at: April 16, 2026, 11:37 a.m.