Triple

T38584372
Position Surface form Disambiguated ID Type / Status
Subject Sunwell Plateau E932312 entity
Predicate requiresAttunementAtLaunch P99625 FINISHED
Object true 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: true | Statement: [Sunwell Plateau, requiresAttunementAtLaunch, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: requiresAttunementAtLaunch
Context triple: [Sunwell Plateau, requiresAttunementAtLaunch, true]
  • A. requiresAttunementOriginal chosen
    Indicates that the item or effect necessitates attunement by a creature before its full properties or benefits can be used.
  • B. requiresWielder
    Indicates that something can only be used, activated, or function properly when it has an associated wielder or user.
  • C. hasRitualFocus
    Indicates that an entity is associated with or directed toward a particular object, practice, or element that serves as the central focus of a ritual.
  • D. requiresPortalOfPower
    Indicates that performing this action or relationship is only possible through or by using a specific portal of power.
  • E. hasRitualElements
    Indicates that one entity incorporates, contains, or is characterized by ritualistic components, practices, or features associated with formalized ceremonies or rites.
  • 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_6a00b8e0a5508190abc5c1e492bed12e completed May 10, 2026, 4:57 p.m.
PD Predicate disambiguation batch_6a00b8327d048190850af317f60f0f8b completed May 10, 2026, 4:54 p.m.
Created at: May 3, 2026, 4:32 p.m.