Triple
T37873034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BlizzCon 2011 |
E944650
|
entity |
| Predicate | hasInGameItem |
P203200
|
FINISHED |
| Object | World of Warcraft Murkablo pet |
—
|
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 Murkablo pet | Statement: [BlizzCon 2011, hasInGameItem, World of Warcraft Murkablo pet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInGameItem Context triple: [BlizzCon 2011, hasInGameItem, World of Warcraft Murkablo pet]
-
A.
hasInGameItemType
Indicates that an entity possesses or is associated with a specific type or category of in-game item.
-
B.
hasInGameID
Indicates that an entity is associated with a specific identifier used to reference it within a game.
-
C.
hasInGameCategory
Indicates that an in-game item, action, or entity belongs to a specific predefined category within the game’s classification system.
-
D.
hasInGameSign
Indicates that an entity is represented or referenced by a sign or signage within a game environment.
-
E.
hasInGameService
Indicates that one entity provides or is associated with a service that is available or usable within a game environment.
- 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_6a013a251b4081908b43d85dd95586c5 |
completed | May 11, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_6a0137e4ea988190812173a5ff044098 |
completed | May 11, 2026, 1:59 a.m. |
| PDg | Predicate description generation | batch_6a013a24495c8190b1035e40c51559d1 |
completed | May 11, 2026, 2:08 a.m. |
Created at: May 3, 2026, 4:19 p.m.