Triple
T6385121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ragnar |
E143680
|
entity |
| Predicate | hasCognate |
P2525
|
FINISHED |
| Object | Ragnarus |
E143680
|
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: Ragnarus | Statement: [Ragnar, hasCognate, Ragnarus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ragnarus Context triple: [Ragnar, hasCognate, Ragnarus]
-
A.
Garmr
Garmr is a fearsome hound from Norse mythology, often associated with guarding the underworld and playing a pivotal role in the events of Ragnarök.
-
B.
Ragnar
chosen
Ragnar is a masculine given name of Old Norse origin, historically associated with Viking-age Scandinavia and later borne by various notable figures.
-
C.
Tyr
Tyr is a Norse god associated primarily with law, justice, and heroic courage, famously known for sacrificing his hand to the wolf Fenrir.
-
D.
Mardöll
Mardöll is an epithet of the Norse goddess Freyja, highlighting her radiant, jewel-like beauty and association with love and fertility.
-
E.
Heorogar
Heorogar is a legendary Danish prince from the Old English epic Beowulf, known as the elder brother of King Hrothgar and a member of the royal Scylding dynasty.
- 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_69c008dac1ec81909cef8157ccd69962 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0686764648190864163d390db292d |
completed | March 22, 2026, 10:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c640b7e89881908e1c39d45e8a8473 |
completed | March 27, 2026, 8:32 a.m. |
Created at: March 22, 2026, 4:34 p.m.