Triple
T37462226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fire Plume's Heart |
E930945
|
entity |
| Predicate | heroPowerTargeting |
P190541
|
FINISHED |
| Object | Random enemy |
—
|
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: Random enemy | Statement: [Fire Plume's Heart, heroPowerTargeting, Random enemy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heroPowerTargeting Context triple: [Fire Plume's Heart, heroPowerTargeting, Random enemy]
-
A.
heroPower
Indicates that an entity possesses or is associated with a particular heroic power or special ability.
-
B.
heroPowerEffect
Indicates the specific impact or outcome that a hero’s power has when it is used.
-
C.
heroPowerName
Indicates the specific power or ability associated with a hero.
-
D.
heroPowerDamage
Indicates that a hero inflicts a certain amount of damage using their special power on a target.
-
E.
powerTarget
Indicates that an entity is the intended recipient or object of another entity’s power, influence, or energy.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcc7779d248190afdb348a95375443 |
completed | May 7, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
| PDg | Predicate description generation | batch_69fcc73264e08190b0b5917f32226fae |
completed | May 7, 2026, 5:09 p.m. |
Created at: May 3, 2026, 4:17 p.m.