Triple

T38584304
Position Surface form Disambiguated ID Type / Status
Subject Hyjal Summit E932311 entity
Predicate attunementQuestlineInvolves P183780 FINISHED
Object The Battle of Mount Hyjal NE NERFINISHED

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: The Battle of Mount Hyjal | Statement: [Hyjal Summit, attunementQuestlineInvolves, The Battle of Mount Hyjal]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: attunementQuestlineInvolves
Context triple: [Hyjal Summit, attunementQuestlineInvolves, The Battle of Mount Hyjal]
  • A. requiresAttunementOriginal
    Indicates that the item or effect necessitates attunement by a creature before its full properties or benefits can be used.
  • B. questlineFeature chosen
    Indicates that something is a notable element, step, or component within a larger questline or narrative progression.
  • C. hasRitualEcho
    Indicates that an action, event, or practice is mirrored, repeated, or symbolically reflected as a ritual counterpart in another context or time.
  • D. questlineAvailableIn
    Indicates that a particular questline can be accessed or played within a specified game, mode, or context.
  • E. questContent
    Indicates that one entity is the content, objective, or narrative substance of a quest associated with another entity.
  • 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_69fcdaa36f90819093f8661969990c7d completed May 7, 2026, 6:32 p.m.
PD Predicate disambiguation batch_69fcd8fefc588190b063d7ea1ec87b07 completed May 7, 2026, 6:25 p.m.
Created at: May 3, 2026, 4:32 p.m.