Triple
T37462240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fire Plume's Heart |
E930945
|
entity |
| Predicate | rewardReplacesBaseHeroPower |
P118328
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Fire Plume's Heart, rewardReplacesBaseHeroPower, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rewardReplacesBaseHeroPower Context triple: [Fire Plume's Heart, rewardReplacesBaseHeroPower, Yes]
-
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.
replacesPowerUp
chosen
Indicates that one power-up is substituted for or takes the place of another in a given context or state.
-
C.
heroPowerEffect
Indicates the specific impact or outcome that a hero’s power has when it is used.
-
D.
powerUp
Indicates an action where an entity increases or restores another entity’s energy, strength, or functional capacity.
-
E.
gainedPowerAfter
Indicates that one entity acquired power, authority, or influence subsequent to an event, condition, or action involving 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_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.