Triple
T38585220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patch 2.1 – Black Temple |
E932330
|
entity |
| Predicate | introducedAttunementChange |
P19084
|
FINISHED |
| Object | Serpentshrine Cavern attunement removal |
—
|
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: Serpentshrine Cavern attunement removal | Statement: [Patch 2.1 – Black Temple, introducedAttunementChange, Serpentshrine Cavern attunement removal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedAttunementChange Context triple: [Patch 2.1 – Black Temple, introducedAttunementChange, Serpentshrine Cavern attunement removal]
-
A.
removedAttunement
Indicates that an existing attunement or connection between entities has been taken away or terminated.
-
B.
requiresAttunementOriginal
Indicates that the item or effect necessitates attunement by a creature before its full properties or benefits can be used.
-
C.
tacticalChange
Indicates a deliberate adjustment in strategy, methods, or actions made to improve effectiveness in a specific situation or operation.
-
D.
notableRuleChange
chosen
Indicates a significant modification to an established rule or set of rules that meaningfully alters how they apply or are enforced.
-
E.
reintroducedInPatch
Indicates that something previously removed or absent was added back or made available again as part of a specific software patch or update.
- 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_69ff370698ec81909bb1596d7d4112ba |
completed | May 9, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69ff3699b6288190b564839cb05f5cf6 |
completed | May 9, 2026, 1:28 p.m. |
Created at: May 3, 2026, 4:32 p.m.