Triple
T11544308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mage (Hearthstone class) |
E273743
|
entity |
| Predicate | heroPowerEffect |
P99991
|
FINISHED |
| Object | Deal 1 damage to any target |
—
|
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: Deal 1 damage to any target | Statement: [Mage (Hearthstone class), heroPowerEffect, Deal 1 damage to any target]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heroPowerEffect Context triple: [Mage (Hearthstone class), heroPowerEffect, Deal 1 damage to any target]
-
A.
enhancesPowersOf
Indicates that one entity increases, amplifies, or strengthens the abilities or powers of another entity.
-
B.
notablePower
Indicates that an entity possesses a significant or distinguished form of power, influence, or capability that is recognized as noteworthy.
-
C.
powerUp
Indicates an action where an entity increases or restores another entity’s energy, strength, or functional capacity.
-
D.
gainedPowerAfter
Indicates that one entity acquired power, authority, or influence subsequent to an event, condition, or action involving another entity.
-
E.
powerUpBehavior
Indicates how an entity changes state or acts when it gains a power-up or temporary enhancement.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e1d754819089f3b6be3404fa0b |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d8087cbe7c819085680f3d67ccc978 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d822ef46988190a1c360da4ee14fef |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:37 p.m.