Triple
T37511261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Graviton Surge |
E932521
|
entity |
| Predicate | associatedHeroRole |
P202248
|
FINISHED |
| Object | tank |
—
|
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: tank | Statement: [Graviton Surge, associatedHeroRole, tank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedHeroRole Context triple: [Graviton Surge, associatedHeroRole, tank]
-
A.
associatedPlayerRole
Indicates a relationship where a specific role or function is linked to, or held by, a particular player.
-
B.
belongsToHeroRole
chosen
Indicates that an entity is assigned to or associated with a hero role within a given context or system.
-
C.
gameRoleInHotS
Indicates the specific role or function an entity has within the game Heroes of the Storm (HotS), such as its position or responsibility in gameplay.
-
D.
gameRoleInHearthstone
Indicates that an entity has a specific role or function within the game Hearthstone.
-
E.
roleInRiseOfShadows
Indicates the specific part or function an entity plays within the context of the "Rise of Shadows" event or storyline.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.