Triple
T37470090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zereth Mortis |
E931131
|
entity |
| Predicate | appearsInPatch |
P99620
|
FINISHED |
| Object | Patch 9.2 Eternity’s End |
—
|
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 9.2 Eternity’s End | Statement: [Zereth Mortis, appearsInPatch, Patch 9.2 Eternity’s End]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInPatch Context triple: [Zereth Mortis, appearsInPatch, Patch 9.2 Eternity’s End]
-
A.
introducedInPatch
chosen
Indicates that something (such as a feature, change, or fix) first appeared or became available in a specific software patch.
-
B.
reintroducedInPatch
Indicates that something previously removed or absent was added back or made available again as part of a specific software patch or update.
-
C.
appearsIn
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
-
D.
appearsInVariant
Indicates that an entity is present or occurs within a particular variant or version of another entity.
-
E.
expansionPatch
Indicates that an entity serves as an extension or add-on that enlarges or augments another entity’s existing scope, content, or functionality.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69feba0f09508190b3e871c62b19ec7f |
completed | May 9, 2026, 4:37 a.m. |
| PD | Predicate disambiguation | batch_69feb957fe7c8190969fb31a6d1a59c8 |
completed | May 9, 2026, 4:34 a.m. |
Created at: May 3, 2026, 4:17 p.m.