Triple
T38022601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Rastakhan |
E948680
|
entity |
| Predicate | hearthstoneRole |
P187928
|
FINISHED |
| Object | hero portrait |
—
|
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: hero portrait | Statement: [King Rastakhan, hearthstoneRole, hero portrait]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hearthstoneRole Context triple: [King Rastakhan, hearthstoneRole, hero portrait]
-
A.
gameRoleInHearthstone
chosen
Indicates that an entity has a specific role or function within the game Hearthstone.
-
B.
roleInWarcraft
Indicates that an entity has a specific character, class, or functional role within the Warcraft universe or game setting.
-
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.
roleInShadowlands
Indicates that one entity has a specific function, position, or significance within the context of the Shadowlands.
-
E.
showdown!Role
Indicates a role or function that an entity assumes or performs within the context of a showdown or competitive confrontation.
- 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_69f76efc10448190aff5fb566b98f952 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 3, 2026, 4:20 p.m.