Triple
T20346444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Æschere |
E495883
|
entity |
| Predicate | memberOf |
P10
|
FINISHED |
| Object | Hrothgar's court |
—
|
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: Hrothgar's court | Statement: [Æschere, memberOf, Hrothgar's court]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hrothgar's court Context triple: [Æschere, memberOf, Hrothgar's court]
-
A.
Heorot
chosen
Heorot is the great mead hall in the Old English epic Beowulf, famed as King Hrothgar’s royal hall and the site of Grendel’s attacks.
-
B.
Meduseld
Meduseld is the great golden hall of the kings of Rohan in J.R.R. Tolkien’s Middle-earth, serving as the royal seat in the city of Edoras.
-
C.
Giant’s Hall
Giant’s Hall is a grand ceremonial hall within Dresden Castle, renowned for its impressive scale and historic role in courtly events and gatherings.
-
D.
Geirröd’s hall
Geirröd’s hall is the imposing stronghold of the giant Geirröd in Norse mythology, known as the setting for his fateful encounter with the god Thor.
-
E.
Harlindon
Harlindon is a coastal region in J.R.R. Tolkien’s Middle-earth, forming part of the elven realm of Lindon west of the Blue Mountains.
- 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_69e0b4a3320881909495ae8bc30bc2dc |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6783937a48190ac86e4959a781a2b |
completed | April 20, 2026, 7:02 p.m. |
Created at: April 16, 2026, 11:24 a.m.