Triple

T1781997
Position Surface form Disambiguated ID Type / Status
Subject Thor: Ragnarok E39309 entity
Predicate mainCharacter P1183 FINISHED
Object Loki E72964 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: Loki | Statement: [Thor: Ragnarok, mainCharacter, Loki]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Loki
Context triple: [Thor: Ragnarok, mainCharacter, Loki]
  • A. Loki chosen
    Loki is a trickster god in Norse mythology known for his shape-shifting, cunning, and role in both aiding and undermining the other gods.
  • B. Thanos
    Thanos is a powerful cosmic warlord from Marvel Comics and the Marvel Cinematic Universe, obsessed with balancing the universe by wiping out half of all life using the Infinity Stones.
  • C. Heimdall
    Heimdall is a powerful Asgardian guardian in the Marvel universe, known for his all-seeing vision, immense strength, and duty to watch over the Bifröst Bridge.
  • D. Jormungandr
    Jormungandr is the colossal World Serpent of Norse mythology, destined to encircle Midgard and battle Thor during Ragnarök.
  • E. Ragnar
    Ragnar is a masculine given name of Old Norse origin, historically associated with Viking-age Scandinavia and later borne by various notable 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_69a88630519c8190a17addd83c4a3ef4 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69aa64e34fe881908aa75f2b4141b87b completed March 6, 2026, 5:23 a.m.
NED1 Entity disambiguation (via context triple) batch_69adb5cbefec8190940cf2a4f692394e completed March 8, 2026, 5:45 p.m.
Created at: March 4, 2026, 7:31 p.m.