Triple

T37470737
Position Surface form Disambiguated ID Type / Status
Subject Mikanikos E931144 entity
Predicate requiresLevelRange P202203 FINISHED
Object Shadowlands level range 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: Shadowlands level range | Statement: [Mikanikos, requiresLevelRange, Shadowlands level range]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: requiresLevelRange
Context triple: [Mikanikos, requiresLevelRange, Shadowlands level range]
  • A. levelRequirement
    Indicates that one entity specifies the minimum level or threshold another entity must meet in order for an action, access, or condition to be valid.
  • B. requiresSkillLevel
    Indicates that performing or engaging in something depends on possessing at least a specified level of skill.
  • C. requiresSubjectsAtLevel
    Indicates that an entity depends on other subjects being present or qualified at a specified level in order for a condition, action, or state to be valid or achievable.
  • D. definesRequirementLevel
    Indicates that one entity specifies or assigns the degree or strictness of obligation required for another entity.
  • E. combatLevelRange
    Indicates the range of combat levels within which two entities can validly or effectively engage in combat with each other.
  • 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_69f76ec2af148190897d101070d7f415 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_6a0061454944819088a0babfe60f69fc completed May 10, 2026, 10:43 a.m.
PD Predicate disambiguation batch_6a0060b9ee108190b91e8d99a16f2b30 completed May 10, 2026, 10:40 a.m.
PDg Predicate description generation batch_6a0061448f6881908daa9fb0da9abefe completed May 10, 2026, 10:43 a.m.
Created at: May 3, 2026, 4:17 p.m.