Triple
T37874341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Necromancer (Diablo Immortal) |
E944679
|
entity |
| Predicate | hasUltimateSkill |
P82038
|
FINISHED |
| Object | Hungering Soulfire |
—
|
NE NERFINISHED |
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: Hungering Soulfire | Statement: [Necromancer (Diablo Immortal), hasUltimateSkill, Hungering Soulfire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUltimateSkill Context triple: [Necromancer (Diablo Immortal), hasUltimateSkill, Hungering Soulfire]
-
A.
ultimateAbility
chosen
Indicates that an entity possesses or uses its most powerful, defining special ability or move.
-
B.
hasEponymousSkill
Indicates that an entity possesses a skill that is named after a particular person or entity.
-
C.
hasProtagonistAbility
Indicates that a protagonist possesses a specific ability, power, or special skill.
-
D.
hasCharacterAbility
Indicates that a character possesses or can perform a specific ability.
-
E.
hasSkillTree
Indicates that an entity is associated with a structured progression of skills or abilities, typically organized in a branching or hierarchical form.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.