Triple
T38061186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assassin (Diablo II) |
E950343
|
entity |
| Predicate | canUseSkill |
P9928
|
FINISHED |
| Object | Dragon Talon |
—
|
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: Dragon Talon | Statement: [Assassin (Diablo II), canUseSkill, Dragon Talon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canUseSkill Context triple: [Assassin (Diablo II), canUseSkill, Dragon Talon]
-
A.
canUseHero
Indicates that an entity is permitted or able to use a specified hero character.
-
B.
canUseSkillGems
Indicates that an entity is able to equip or activate specified skill gems to gain or use their associated abilities.
-
C.
canUse
chosen
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
D.
canBeUsed
Indicates that one entity is suitable or available to serve a particular function, purpose, or role in relation to another entity or context.
-
E.
skillUsedFor
Indicates that a particular skill is employed or applied to perform, achieve, or facilitate a specific task, goal, or function.
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.