Triple

T38585212
Position Surface form Disambiguated ID Type / Status
Subject Patch 2.1 – Black Temple E932330 entity
Predicate introducedDungeonChanges P199281 FINISHED
Object Heroic dungeon difficulty adjustments 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: Heroic dungeon difficulty adjustments | Statement: [Patch 2.1 – Black Temple, introducedDungeonChanges, Heroic dungeon difficulty adjustments]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: introducedDungeonChanges
Context triple: [Patch 2.1 – Black Temple, introducedDungeonChanges, Heroic dungeon difficulty adjustments]
  • A. addsPublicDungeon
    Indicates that an entity introduces or includes a public dungeon as part of its content or structure.
  • B. addedBattlegroundChanges
    Indicates that modifications or updates have been made to a battleground or battlefield configuration.
  • C. dungeonCountAtLaunch
    Indicates the number of dungeons available when the game or content is first released.
  • D. notableDungeon
    Indicates that an entity is recognized as a significant or noteworthy dungeon, typically due to its importance, uniqueness, or prominence.
  • E. hasDungeon
    Indicates that one entity possesses, contains, or includes a dungeon as part of its structure, property, or domain.
  • F. None of above. chosen

Provenance (4 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_69ff29d831b881908d485609e0fc1d0b completed May 9, 2026, 12:34 p.m.
PD Predicate disambiguation batch_69ff28f9f9e4819087f3402735de66c7 completed May 9, 2026, 12:30 p.m.
PDg Predicate description generation batch_69ff29d77f48819085304ed5e92eb906 completed May 9, 2026, 12:34 p.m.
Created at: May 3, 2026, 4:32 p.m.