Triple
T19978699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freawaru |
E493757
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | Hrothmund |
—
|
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: Hrothmund | Statement: [Freawaru, relatedTo, Hrothmund]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hrothmund Context triple: [Freawaru, relatedTo, Hrothmund]
-
A.
Hrothmund
chosen
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.
-
B.
Hrodulf
Hrodulf is a Germanic given name of ancient origin that forms the etymological root of the modern name Rudolph.
-
C.
Orpund
Orpund is a municipality in the canton of Bern in Switzerland, situated near the city of Biel/Bienne.
-
D.
Sigfrid
Sigfrid is a masculine given name of Scandinavian origin, notably borne by Swedish industrialist and long-serving International Olympic Committee president Sigfrid Edström.
-
E.
Ingemund
Ingemund is a Scandinavian masculine given name of Old Norse origin, historically borne by several notable figures in Sweden and Norway.
- 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.