Triple
T37458210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Thunder King |
E930851
|
entity |
| Predicate | hasHeroPowerType |
P99992
|
FINISHED |
| Object | Shaman hero power |
—
|
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: Shaman hero power | Statement: [The Thunder King, hasHeroPowerType, Shaman hero power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeroPowerType Context triple: [The Thunder King, hasHeroPowerType, Shaman hero power]
-
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.
usesPowerType
Indicates that one entity operates or functions by means of a specified type or source of power.
-
C.
heroPower
chosen
Indicates that an entity possesses or is associated with a particular heroic power or special ability.
-
D.
heroPowerEffect
Indicates the specific impact or outcome that a hero’s power has when it is used.
-
E.
heroPowerName
Indicates the specific power or ability associated with a hero.
- 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_69fe031bc6208190860099aef72d8dcb |
completed | May 8, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69fe014c8b388190b5d4e0cb95ee2be5 |
completed | May 8, 2026, 3:29 p.m. |
Created at: May 3, 2026, 4:17 p.m.