Triple

T38591603
Position Surface form Disambiguated ID Type / Status
Subject Scepter of the Shifting Sands E932465 entity
Predicate requiresNPC P202868 FINISHED
Object Eranikus
Eranikus is a powerful green dragon from World of Warcraft lore, known as a corrupted lieutenant of Ysera and a key figure in several classic raid and quest storylines.
E2277220 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: Eranikus | Statement: [Scepter of the Shifting Sands, requiresNPC, Eranikus]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Eranikus
Triple: [Scepter of the Shifting Sands, requiresNPC, Eranikus]
Generated description
Eranikus is a powerful green dragon from World of Warcraft lore, known as a corrupted lieutenant of Ysera and a key figure in several classic raid and quest storylines.

Provenance (5 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_69f76ec654d48190b421111cf26e54d9 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_6a00c93a88a881908a7700fd1410489f completed May 10, 2026, 6:06 p.m.
NED1 Entity disambiguation (via context triple) batch_6a41eaa06eac8190a8794328b411ad27 completed June 29, 2026, 3:46 a.m.
NEDg Description generation batch_6a41ed404f2c8190a55b0f41d4804fd1 completed June 29, 2026, 3:57 a.m.
NED2 Entity disambiguation (via description) batch_6a41eda6cc8481908e36bc22a5199689 completed June 29, 2026, 3:59 a.m.
Created at: May 3, 2026, 4:32 p.m.