Triple
T37465386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Priestess of Fury |
E931020
|
entity |
| Predicate | associatedClassHero |
P100346
|
FINISHED |
| Object | Illidan Stormrage |
E932327
|
NE 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: Illidan Stormrage | Statement: [Priestess of Fury, associatedClassHero, Illidan Stormrage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedClassHero Context triple: [Priestess of Fury, associatedClassHero, Illidan Stormrage]
-
A.
heroClass
chosen
Indicates the character class or role that a hero belongs to within a given system or context.
-
B.
linkedHero
Indicates a relationship where one hero is associated or connected to another hero in a meaningful way.
-
C.
associatedWithSuperhero
Indicates that one entity has a notable connection, link, or involvement with a superhero entity.
-
D.
associatedEpicHero
Indicates a relationship where one entity is linked to, or thematically connected with, a particular epic hero.
-
E.
includesHeroes
Indicates that something (such as a work, group, or collection) contains or features one or more heroes as part of it.
- F. None of above.
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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41852701608190b52cab3f46b40600 |
completed | June 28, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.