Triple

T35830652
Position Surface form Disambiguated ID Type / Status
Subject Sargeras E1035787 entity
Predicate notableServant P198619 FINISHED
Object Mannoroth
Mannoroth is a powerful pit lord demon from the Warcraft universe, infamous for corrupting the orcish race with demonic blood and serving as a high-ranking commander of the Burning Legion.
E2160736 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: Mannoroth | Statement: [Sargeras, notableServant, Mannoroth]
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: Mannoroth
Triple: [Sargeras, notableServant, Mannoroth]
Generated description
Mannoroth is a powerful pit lord demon from the Warcraft universe, infamous for corrupting the orcish race with demonic blood and serving as a high-ranking commander of the Burning Legion.

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_69f76e192a94819082db360cb91e6a8d completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69fef96e349c8190b41edc78c16540c6 completed May 9, 2026, 9:07 a.m.
NED1 Entity disambiguation (via context triple) batch_6a38ae18063c8190aa30948e1c8c21cd completed June 22, 2026, 3:38 a.m.
NEDg Description generation batch_6a38aea905748190981128825afb9fbe completed June 22, 2026, 3:40 a.m.
NED2 Entity disambiguation (via description) batch_6a38af0c461c8190a7332d1709b5553c completed June 22, 2026, 3:42 a.m.
Created at: May 3, 2026, 4:06 p.m.