Triple
T38585256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patch 2.4 – Fury of the Sunwell |
E932331
|
entity |
| Predicate | addedClassChanges |
P189102
|
FINISHED |
| Object | multiple class balance adjustments |
—
|
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: multiple class balance adjustments | Statement: [Patch 2.4 – Fury of the Sunwell, addedClassChanges, multiple class balance adjustments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addedClassChanges Context triple: [Patch 2.4 – Fury of the Sunwell, addedClassChanges, multiple class balance adjustments]
-
A.
addsClass
Indicates that one entity introduces or appends a class (such as a classification, type, or code) to another entity.
-
B.
addedInUpdate
chosen
Indicates that something was introduced or became available as part of a specific update or version change.
-
C.
addsDimensionChange
Indicates that one entity introduces or applies a change to the dimensional properties (such as size, scale, or number of dimensions) of another entity.
-
D.
changesWith
Indicates that one entity varies or is modified in response to changes in another entity.
-
E.
changedAfter
Indicates that one entity underwent a change at a point in time that is later than the time at which another referenced entity changed.
- 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_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:32 p.m.