Triple
T37458187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Vashj |
E930850
|
entity |
| Predicate | roleInHearthstone |
P187928
|
FINISHED |
| Object | alternate Shaman hero |
—
|
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: alternate Shaman hero | Statement: [Lady Vashj, roleInHearthstone, alternate Shaman hero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInHearthstone Context triple: [Lady Vashj, roleInHearthstone, alternate Shaman hero]
-
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.
roleInShadowlands
Indicates that one entity has a specific function, position, or significance within the context of the Shadowlands.
-
D.
roleInWarcraftIII
Indicates the specific function, position, or part an entity plays within the context of Warcraft III (e.g., in its story, gameplay, or production).
-
E.
roleInDominion
Indicates that an entity holds a specific role, position, or function within a particular dominion, realm, or sphere of authority.
- 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_6a0212b3462c8190ba3587852cb10655 |
completed | May 11, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_6a020f3138a48190ac630e810939e881 |
completed | May 11, 2026, 5:17 p.m. |
Created at: May 3, 2026, 4:17 p.m.