Triple

T20490832
Position Surface form Disambiguated ID Type / Status
Subject Dragons E502736 entity
Predicate notableExample P1503 FINISHED
Object Fafnir 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: Fafnir | Statement: [Dragons, notableExample, Fafnir]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fafnir
Context triple: [Dragons, notableExample, Fafnir]
  • A. Fáfnir chosen
    Fáfnir is a fearsome dragon from Norse mythology, originally a dwarf transformed by greed, who is slain by the hero Sigurd.
  • B. Níðhǫggr
    Níðhǫggr is a dragon or serpent in Norse mythology that gnaws at the roots of the world tree Yggdrasil and is associated with destruction and the punishment of the wicked.
  • C. 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.
  • D. Sigfred
    Sigfred was a Viking leader known for commanding Norse forces during the late 9th-century siege of Paris.
  • E. Sigurd Hring
    Sigurd Hring is a legendary Scandinavian king and warrior of Norse sagas, often associated with the early Viking Age and linked to the lineage of the famed hero Ragnar Lodbrok.
  • 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_69e0b4b0373881909dd3e9387f82eab4 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e69cb8e7848190a1dc497a10ae798c completed April 20, 2026, 9:38 p.m.
Created at: April 16, 2026, 11:35 a.m.