Triple
T37592244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loatheb |
E935287
|
entity |
| Predicate | HearthstoneEffect |
P188710
|
FINISHED |
| Object | increases cost of enemy spells next turn |
—
|
LITERAL FINISHED |
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: increases cost of enemy spells next turn | Statement: [Loatheb, HearthstoneEffect, increases cost of enemy spells next turn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HearthstoneEffect Context triple: [Loatheb, HearthstoneEffect, increases cost of enemy spells next turn]
-
A.
hasHeroPower
Indicates that one entity possesses or is endowed with a special ability or power characteristic of a hero in relation to another entity.
-
B.
cardEffect
chosen
Indicates that one card produces a specific effect or outcome on another entity or the game state.
-
C.
heroPowerEffect
Indicates the specific impact or outcome that a hero’s power has when it is used.
-
D.
cardEffectTarget
Indicates that a particular effect of a card is directed toward or applied to a specified target.
-
E.
magicTrigger
Indicates that one entity initiates or activates a magical effect, condition, or event upon another entity or context.
- 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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.