Triple

T38586239
Position Surface form Disambiguated ID Type / Status
Subject Third War E932351 entity
Predicate notableBattle P259 FINISHED
Object Siege of Dalaran
The Siege of Dalaran was a major Warcraft III campaign event in which the Scourge and Burning Legion assaulted the mage city of Dalaran to claim the powerful spellbook of Medivh.
E2277585 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: Siege of Dalaran | Statement: [Third War, notableBattle, Siege of Dalaran]
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: Siege of Dalaran
Triple: [Third War, notableBattle, Siege of Dalaran]
Generated description
The Siege of Dalaran was a major Warcraft III campaign event in which the Scourge and Burning Legion assaulted the mage city of Dalaran to claim the powerful spellbook of Medivh.

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_69fcd938241481909d31fa1056a27a21 completed May 7, 2026, 6:26 p.m.
NED1 Entity disambiguation (via context triple) batch_6a41f43924cc8190b03f5c8d442f4e7f completed June 29, 2026, 4:27 a.m.
NEDg Description generation batch_6a41f4d0afe4819093c6b93163cddfe5 completed June 29, 2026, 4:30 a.m.
NED2 Entity disambiguation (via description) batch_6a41f54e7d6c81909bac42ff59a0e27e completed June 29, 2026, 4:32 a.m.
Created at: May 3, 2026, 4:32 p.m.