Triple

T37465553
Position Surface form Disambiguated ID Type / Status
Subject Kanrethad Ebonlocke E931024 entity
Predicate roleInWoW P117259 FINISHED
Object major antagonist in the warlock green fire quest 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: major antagonist in the warlock green fire quest | Statement: [Kanrethad Ebonlocke, roleInWoW, major antagonist in the warlock green fire quest]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleInWoW
Context triple: [Kanrethad Ebonlocke, roleInWoW, major antagonist in the warlock green fire quest]
  • A. roleInWarcraft chosen
    Indicates that an entity has a specific character, class, or functional role within the Warcraft universe or game setting.
  • B. roleInWarcraftIII
    Indicates the specific function, position, or part an entity plays within the context of Warcraft III (e.g., in its story, gameplay, or production).
  • C. roleAtRagnarok
    Indicates the specific function, position, or part an entity is expected to have or perform during Ragnarok.
  • D. gameRoleInHearthstone
    Indicates that an entity has a specific role or function within the game Hearthstone.
  • E. roleInLegendarium
    Indicates that one entity serves a particular narrative or functional role within the fictional mythos or legendarium associated with another entity.
  • 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_69f76ec2af148190897d101070d7f415 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_6a022348ae2881908eae1be79b6f6ff6 completed May 11, 2026, 6:43 p.m.
PD Predicate disambiguation batch_6a0220beb6b08190981fb86363757517 completed May 11, 2026, 6:32 p.m.
Created at: May 3, 2026, 4:17 p.m.