Triple
T37457260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hero Power Mage |
E930829
|
entity |
| Predicate | usesHero |
P31799
|
FINISHED |
| Object | Mage default hero power Fireblast |
—
|
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: Mage default hero power Fireblast | Statement: [Hero Power Mage, usesHero, Mage default hero power Fireblast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHero Context triple: [Hero Power Mage, usesHero, Mage default hero power Fireblast]
-
A.
includesHeroes
Indicates that something (such as a work, group, or collection) contains or features one or more heroes as part of it.
-
B.
nativeHero
Indicates that an entity is regarded as a heroic figure originating from or strongly associated with a particular place or community.
-
C.
heroPower
Indicates that an entity possesses or is associated with a particular heroic power or special ability.
-
D.
usedByCharacter
chosen
Indicates that something (such as an item, ability, or resource) is utilized or employed by a particular character.
-
E.
heroDepicted
Indicates that one entity is portrayed or represented as a hero in relation to another entity.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.