Triple

T8148230
Position Surface form Disambiguated ID Type / Status
Subject Sigmund E190266 entity
Predicate isRelatedName P3889 FINISHED
Object Sigfryd E435371 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: Sigfryd | Statement: [Sigmund, isRelatedName, Sigfryd]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sigfryd
Context triple: [Sigmund, isRelatedName, Sigfryd]
  • A. Sigurd Slembe
    Sigurd Slembe is a historical drama by Norwegian writer Bjørnstjerne Bjørnson that portrays the turbulent life of the 12th-century Norwegian pretender Sigurd Slembe.
  • B. Tyr
    Tyr is a Norse god associated primarily with law, justice, and heroic courage, famously known for sacrificing his hand to the wolf Fenrir.
  • C. Berserker
    Berserker is a series of science fiction stories by Fred Saberhagen about relentless, self-replicating war machines bent on exterminating all life in the galaxy.
  • D. 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.
  • E. Sigurd chosen
    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_69ca82be7ba8819087de0147e9292c83 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb447e74e081908df774edb2134209 completed March 31, 2026, 3:50 a.m.
NED1 Entity disambiguation (via context triple) batch_69ccbee697208190a1d9c98b2a4414bd completed April 1, 2026, 6:44 a.m.
Created at: March 30, 2026, 5:36 p.m.