Triple

T37507226
Position Surface form Disambiguated ID Type / Status
Subject Desmotaeron E932126 entity
Predicate designedForPlayerLevelRange P100059 FINISHED
Object max-level characters in Shadowlands 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: max-level characters in Shadowlands | Statement: [Desmotaeron, designedForPlayerLevelRange, max-level characters in Shadowlands]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: designedForPlayerLevelRange
Context triple: [Desmotaeron, designedForPlayerLevelRange, max-level characters in Shadowlands]
  • A. intendedPlayerLevel chosen
    Indicates the player level for which something (such as content, an item, or a challenge) is designed or meant to be used.
  • B. combatLevelRange
    Indicates the range of combat levels within which two entities can validly or effectively engage in combat with each other.
  • C. gearItemLevelRange
    Indicates the range of item levels that a piece of gear can or does fall within.
  • D. recommendedLevelRangeRetail
    Indicates the range of levels at which a product is recommended to be sold or used in a retail context.
  • E. typicalAgeRangeOfPlayers
    Indicates the usual age range of people who typically play or participate in something.
  • 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_69f76ec5268481909ea01c73aeeefd42 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69ff7ae5d088819089aa3b6360b6b749 completed May 9, 2026, 6:20 p.m.
PD Predicate disambiguation batch_69ff7a4df6488190bf60d675b36b1d6d completed May 9, 2026, 6:17 p.m.
Created at: May 3, 2026, 4:17 p.m.