Triple
T19978640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hrothmund |
E493756
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Scylding |
—
|
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: Scylding | Statement: [Hrothmund, familyName, Scylding]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Scylding Context triple: [Hrothmund, familyName, Scylding]
-
A.
Scylding
chosen
The Scyldings are a legendary royal dynasty of Danish rulers prominently featured in the Old English epic poem "Beowulf."
-
B.
Hygelac
Hygelac is the legendary king of the Geats and uncle to the hero Beowulf in the Old English epic poem.
-
C.
Ragnar Lodbrok
Ragnar Lodbrok is a legendary Viking hero and king of Scandinavian sagas, famed for his raids on England and France and his dramatic, mythologized death.
-
D.
Sigurd the Mighty
Sigurd the Mighty was a 9th-century Norse warlord famed for his brutal conquests in northern Scotland and legendary death after being wounded by a severed enemy head.
-
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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65d11108481908241a2a96a795a7d |
completed | April 20, 2026, 5:06 p.m. |
Created at: April 11, 2026, 3:27 p.m.