Triple
T38643841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heart of Azeroth |
E938667
|
entity |
| Predicate | modifiedInPatch |
P60216
|
FINISHED |
| Object | World of Warcraft patch 8.2.0 |
—
|
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: World of Warcraft patch 8.2.0 | Statement: [Heart of Azeroth, modifiedInPatch, World of Warcraft patch 8.2.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modifiedInPatch Context triple: [Heart of Azeroth, modifiedInPatch, World of Warcraft patch 8.2.0]
-
A.
modifiedAs
Indicates that one entity has been altered, changed, or revised into another form, version, or state.
-
B.
modificationBy
Indicates that one entity has been altered, changed, or adjusted as a result of an action performed by another entity.
-
C.
updatedIn
chosen
Indicates that an entity has undergone a change or modification within a specified time period or version context.
-
D.
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.
-
E.
laterModification
Indicates that one entity is a modification or revision that occurs after another in time.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.