Triple

T15396724
Position Surface form Disambiguated ID Type / Status
Subject World Serpent E368195 entity
Predicate alsoKnownAs P39 FINISHED
Object Midgard Serpent E74276 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: Midgard Serpent | Statement: [World Serpent, alsoKnownAs, Midgard Serpent]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Midgard Serpent
Context triple: [World Serpent, alsoKnownAs, Midgard Serpent]
  • A. Jormungandr chosen
    Jormungandr is the colossal World Serpent of Norse mythology, destined to encircle Midgard and battle Thor during Ragnarök.
  • B. Svarog
    Svarog is the Slavic god of the sky, fire, and blacksmithing, often regarded as a creator deity and divine craftsman.
  • C. Níðhöggr
    Níðhöggr is a fearsome dragon or serpent from Norse mythology that gnaws at the roots of the world tree Yggdrasil and is associated with chaos and destruction.
  • D. Skarasen
    Skarasen is a gigantic, cybernetically controlled aquatic creature from Doctor Who, often associated with the Loch Ness Monster myth and used as a living weapon by the Zygons.
  • E. Midgard
    Midgard is the human-inhabited world in Norse mythology, situated between the realms of gods and giants and encircled by a vast ocean.
  • 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_69d85a16c68c819099c1b547fbc87b32 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e03e8c5d40819086622b70edcb6294 completed April 16, 2026, 1:42 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff364f8ab481909f88e6b5fb42cd19 completed May 9, 2026, 1:27 p.m.
Created at: April 10, 2026, 3:19 a.m.