Triple
T37457719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shadowreaper Anduin |
E930839
|
entity |
| Predicate | relatedKeyword |
—
|
GENERATED |
| Object | Hero Power refresh |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedKeyword Context triple: [Shadowreaper Anduin, relatedKeyword, Hero Power refresh]
-
A.
associatedKeyword
chosen
Indicates that one entity is linked to or characterized by a particular keyword used for identification, categorization, or retrieval.
-
B.
relatedPass
Indicates that one pass is associated with or connected to another pass in some relevant way.
-
C.
relatedToTerm
Indicates a general, non-specific relationship or association between one term and another.
-
D.
relatedMatchType
Indicates that two entities are connected through a specified type or category of relationship that defines how they are considered related or matched.
-
E.
relatedTLD
Indicates that one top-level domain (TLD) has an association or connection with another TLD, such as similarity, shared purpose, or contextual relevance.
- F. None of above.
Provenance (1 batch)
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. |
Created at: May 3, 2026, 4:17 p.m.