Triple

T38584405
Position Surface form Disambiguated ID Type / Status
Subject Hellfire Ramparts E932313 entity
Predicate recommendedLevelRangeBurningCrusade P191449 FINISHED
Object 60-62 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: 60-62 | Statement: [Hellfire Ramparts, recommendedLevelRangeBurningCrusade, 60-62]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: recommendedLevelRangeBurningCrusade
Context triple: [Hellfire Ramparts, recommendedLevelRangeBurningCrusade, 60-62]
  • A. combatLevelRange
    Indicates the range of combat levels within which two entities can validly or effectively engage in combat with each other.
  • B. levelRangePreCataclysm
    Indicates the range of character or content levels that applied to something before the Cataclysm event or update.
  • C. intendedPlayerLevel
    Indicates the player level for which something (such as content, an item, or a challenge) is designed or meant to be used.
  • D. recommendedLevelAtLaunch
    Indicates the level that is advised or expected for an entity at the moment it is first introduced or made available.
  • E. 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.
  • 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_69fcdfbc71c481908ba7f87907b17782 completed May 7, 2026, 6:53 p.m.
PD Predicate disambiguation batch_69fcdbe580b8819087f143596b2c79c0 completed May 7, 2026, 6:37 p.m.
PDg Predicate description generation batch_69fcdfbafbf48190abe38ec0003a6419 completed May 7, 2026, 6:53 p.m.
Created at: May 3, 2026, 4:32 p.m.