Triple
T37458293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aggro Shaman |
E930853
|
entity |
| Predicate | playerSkillFocus |
P45342
|
FINISHED |
| Object | Efficient damage calculation |
—
|
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: Efficient damage calculation | Statement: [Aggro Shaman, playerSkillFocus, Efficient damage calculation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerSkillFocus Context triple: [Aggro Shaman, playerSkillFocus, Efficient damage calculation]
-
A.
skillType
Indicates the specific category or kind of skill that characterizes or classifies an associated skill-related entity or action.
-
B.
skillEmphasis
chosen
Indicates that a particular skill is given special focus, priority, or importance within a context such as a role, task, or curriculum.
-
C.
killsAt
Indicates that one entity causes the death of another entity at a specific time or event.
-
D.
sportsSkill
Indicates that an entity possesses a particular ability, proficiency, or level of competence in performing a sport or sports-related activity.
-
E.
skillFactor
Indicates the degree or level of skill associated with an entity in performing a particular task or activity.
- 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_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: May 3, 2026, 4:17 p.m.