Triple
T38584373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunwell Plateau |
E932312
|
entity |
| Predicate | attunementRemovedInPatch |
P191227
|
FINISHED |
| Object | 2.4.2 |
—
|
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: 2.4.2 | Statement: [Sunwell Plateau, attunementRemovedInPatch, 2.4.2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attunementRemovedInPatch Context triple: [Sunwell Plateau, attunementRemovedInPatch, 2.4.2]
-
A.
removedAttunement
chosen
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.
untaps
Indicates that an entity causes another entity, typically one that was previously tapped or exhausted, to return to an active or ready state.
-
D.
featureRemoved
Indicates that a previously existing feature has been taken out, disabled, or is no longer available.
-
E.
laterRemovedTo
Indicates that an entity was moved or transferred to a location or state at a later time, after an earlier condition or placement.
- 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_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:32 p.m.