Triple

T30675416
Position Surface form Disambiguated ID Type / Status
Subject Magik E780895 entity
Predicate hasDemonicForm P117174 FINISHED
Object Darkchylde form with horns, hooves, and tail LITERAL 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: Darkchylde form with horns, hooves, and tail | Statement: [Magik, hasDemonicForm, Darkchylde form with horns, hooves, and tail]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDemonicForm
Context triple: [Magik, hasDemonicForm, Darkchylde form with horns, hooves, and tail]
  • A. hasDemonCharacter chosen
    Indicates that an entity includes or features a character that is a demon.
  • B. hasAntagonistForm
    Indicates that an entity possesses or takes on a form characterized by opposition, hostility, or antagonistic behavior toward another entity.
  • C. isDemonKing
    Indicates that an entity holds the status or role of a demon king, typically as the supreme ruler or most powerful figure among demons.
  • D. isUndead
    Indicates that an entity is no longer living in a natural sense but continues to exist through supernatural or unnatural means.
  • E. hasTotem
    Indicates that one entity possesses, is symbolically represented by, or is associated with another entity as its totem.
  • F. None of above.

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_69f224a7fc208190a07d6d3879b31640 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69fddac4e2f48190a9301d3422658b29 completed May 8, 2026, 12:44 p.m.
PD Predicate disambiguation batch_69fdda06969c8190b5d033964ea2a690 completed May 8, 2026, 12:41 p.m.
Created at: April 29, 2026, 8:32 p.m.