Triple

T38585259
Position Surface form Disambiguated ID Type / Status
Subject Patch 2.4 – Fury of the Sunwell E932331 entity
Predicate addedUIChanges P31366 FINISHED
Object combat log improvements 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: combat log improvements | Statement: [Patch 2.4 – Fury of the Sunwell, addedUIChanges, combat log improvements]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: addedUIChanges
Context triple: [Patch 2.4 – Fury of the Sunwell, addedUIChanges, combat log improvements]
  • A. notableGUIChange chosen
    Indicates a significant modification or redesign in a system’s graphical user interface compared to its previous state.
  • B. addedInUpdate
    Indicates that something was introduced or became available as part of a specific update or version change.
  • C. addsDimensionChange
    Indicates that one entity introduces or applies a change to the dimensional properties (such as size, scale, or number of dimensions) of another entity.
  • D. changedAfter
    Indicates that one entity underwent a change at a point in time that is later than the time at which another referenced entity changed.
  • E. compositionChanged
    Indicates that the makeup or constituent elements of something have been altered from a previous state.
  • 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_69f76ec654d48190b421111cf26e54d9 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fcef654d588190b29ecc76678d1aa0 completed May 7, 2026, 8 p.m.
PD Predicate disambiguation batch_69fcecdb97f48190b382b7d13be92dc0 completed May 7, 2026, 7:49 p.m.
Created at: May 3, 2026, 4:32 p.m.