Triple
T5044045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hrólfr |
E113616
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Hrolf |
E113616
|
NE FINISHED |
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: Hrolf | Statement: [Hrólfr, alsoKnownAs, Hrolf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hrolf Context triple: [Hrólfr, alsoKnownAs, Hrolf]
-
A.
Hrólfr
chosen
Hrólfr, better known as Rollo, was a Viking leader who became the first ruler of Normandy in the early 10th century.
-
B.
Ivar
Ivar is a masculine given name of Old Norse origin, traditionally used in Scandinavian countries.
-
C.
Thorfinn Sigurdsson
Thorfinn Sigurdsson, also known as Thorfinn the Mighty, was an 11th-century Earl of Orkney and powerful Norse ruler in the Northern Isles of Scotland.
-
D.
Alfrid
Alfrid is a masculine given name of Germanic origin, commonly associated with medieval and fantasy settings.
-
E.
Sigurd
Sigurd is a masculine given name of Old Norse origin, historically associated with legendary heroes and figures in Scandinavian culture.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69bd44391fc48190a311ce9c826c209b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73fc04f08190aba851fa0192d0fb |
completed | March 20, 2026, 4:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be9c8ad6408190bf4408af7b095a12 |
completed | March 21, 2026, 1:26 p.m. |
Created at: March 20, 2026, 1:37 p.m.