Triple

T16380177
Position Surface form Disambiguated ID Type / Status
Subject Þorbjörn öngull E397783 entity
Predicate hasNameVariant P457 FINISHED
Object Thorbjorn ongull E1205674 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: Thorbjorn ongull | Statement: [Þorbjörn öngull, hasNameVariant, Thorbjorn ongull]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Thorbjorn ongull
Context triple: [Þorbjörn öngull, hasNameVariant, Thorbjorn ongull]
  • A. Torbjørn
    Torbjørn is a Scandinavian masculine given name, particularly common in Norway, derived from Old Norse elements meaning "Thor" and "bear."
  • B. Thorbjörn Öngull chosen
    Thorbjörn Öngull is a figure from Icelandic saga literature, known as the man who finally slew the outlaw hero Grettir Ásmundarson in Grettis saga.
  • C. Ingvar
    Ingvar is a Scandinavian given name of Old Norse origin, historically associated with Viking-age figures and meaning roughly "Ing’s warrior" or "warrior of the god Ing."
  • D. Gunnar
    Gunnar is a masculine given name of Old Norse origin, commonly used in Scandinavian countries and associated with warriors or bold fighters.
  • E. Halvdan
    Halvdan is a masculine given name of Scandinavian origin, historically borne by several notable Norwegian figures.
  • 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_69d87f2880b48190ae1a9673a3bbef80 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e319db5b648190a8fca23518a1fb39 completed April 18, 2026, 5:42 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0035689ef08190ba980a359498ca56 completed May 10, 2026, 7:36 a.m.
Created at: April 10, 2026, 5:08 a.m.