Triple
T37872270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vale of Eternal Blossoms |
E944634
|
entity |
| Predicate | laterDamagedInPatch |
P203287
|
FINISHED |
| Object | Patch 5.4 Siege of Orgrimmar |
—
|
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: Patch 5.4 Siege of Orgrimmar | Statement: [Vale of Eternal Blossoms, laterDamagedInPatch, Patch 5.4 Siege of Orgrimmar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterDamagedInPatch Context triple: [Vale of Eternal Blossoms, laterDamagedInPatch, Patch 5.4 Siege of Orgrimmar]
-
A.
damagedIn
Indicates that an entity has suffered harm, impairment, or destruction as a result of a specified event, process, or condition.
-
B.
damagedModule
Indicates that a module has been harmed, impaired, or rendered partially or fully nonfunctional.
-
C.
lessDamagedThan
Indicates that one entity has sustained a lower degree of damage than another entity.
-
D.
replacedStructureDamagedBy
Indicates that a structure which has been replaced is (or was) damaged by a specified agent, event, or condition.
-
E.
damagedBy
Indicates that one entity has caused harm, impairment, or deterioration to another entity.
- F. None of above. chosen
Provenance (4 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a0149447e448190b0480943de0691ee |
completed | May 11, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_6a0148e2c39c8190a3ad6ea6be902c04 |
completed | May 11, 2026, 3:11 a.m. |
| PDg | Predicate description generation | batch_6a014943b7d481909fa2c1c3f176db24 |
completed | May 11, 2026, 3:13 a.m. |
Created at: May 3, 2026, 4:19 p.m.