Triple
T38583255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kul Tirans |
E932290
|
entity |
| Predicate | playableFromPatch |
P192698
|
FINISHED |
| Object | World of Warcraft patch 8.1.5 |
—
|
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.1.5 | Statement: [Kul Tirans, playableFromPatch, World of Warcraft patch 8.1.5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playableFromPatch Context triple: [Kul Tirans, playableFromPatch, World of Warcraft patch 8.1.5]
-
A.
playableWith
Indicates that one entity can be used, engaged, or interacted with together alongside another entity, typically in a compatible or cooperative manner.
-
B.
playableInGame
Indicates that something can be used or controlled as an active element within a particular game.
-
C.
playableOffline
Indicates that an item (such as a game or media) can be used or accessed without an active internet connection.
-
D.
playable
Indicates that an entity can be used or performed as a game, media, or activity in its intended interactive or functional form.
-
E.
playableInClass
Indicates that something (such as a skill, item, or ability) can be used or is valid for use within a particular class or category.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
| PDg | Predicate description generation | batch_69fd231bdd108190900369e07c854e95 |
completed | May 7, 2026, 11:41 p.m. |
Created at: May 3, 2026, 4:32 p.m.