Triple

T37551775
Position Surface form Disambiguated ID Type / Status
Subject Dragonblight E933605 entity
Predicate contains P35 FINISHED
Object Wintergarde Keep
Wintergarde Keep is a major Alliance stronghold and quest hub in World of Warcraft, serving as a frontline base against the Scourge in the Dragonblight region of Northrend.
E2240113 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: Wintergarde Keep | Statement: [Dragonblight, contains, Wintergarde Keep]
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: Wintergarde Keep
Triple: [Dragonblight, contains, Wintergarde Keep]
Generated description
Wintergarde Keep is a major Alliance stronghold and quest hub in World of Warcraft, serving as a frontline base against the Scourge in the Dragonblight region of Northrend.

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_69f76eca55bc8190acf25741793d5dac completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fba450f5d881909d8ce6d1abe264a1 completed May 6, 2026, 8:28 p.m.
NED1 Entity disambiguation (via context triple) batch_6a40d665f2b081909d01d83c055d4116 completed June 28, 2026, 8:08 a.m.
NEDg Description generation batch_6a40d8245d408190ae94ab7d5706484f completed June 28, 2026, 8:15 a.m.
NED2 Entity disambiguation (via description) batch_6a40d8820ff48190903a7ee14bad6301 completed June 28, 2026, 8:17 a.m.
Created at: May 3, 2026, 4:17 p.m.