Triple
T37457707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shadowreaper Anduin |
E930839
|
entity |
| Predicate | roleInDecks |
P187928
|
FINISHED |
| Object | Control Priest finisher |
—
|
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: Control Priest finisher | Statement: [Shadowreaper Anduin, roleInDecks, Control Priest finisher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInDecks Context triple: [Shadowreaper Anduin, roleInDecks, Control Priest finisher]
-
A.
roleInDominion
Indicates that an entity holds a specific role, position, or function within a particular dominion, realm, or sphere of authority.
-
B.
roleInRepertoire
Indicates that an entity serves a specific role or function within a larger repertoire, collection, or set of items.
-
C.
roleInGameplay
Indicates the specific function or responsibility an entity has within the context of gameplay or game mechanics.
-
D.
playsInRole
Indicates that an entity performs or appears in a specific role within a production, event, or context.
-
E.
gameRoleInHearthstone
chosen
Indicates that an entity has a specific role or function within the game Hearthstone.
- 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_6a0207a1272c81909dcdb6e3307702f5 |
completed | May 11, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_6a0205fa1e608190829fd2baa0434fff |
completed | May 11, 2026, 4:38 p.m. |
Created at: May 3, 2026, 4:17 p.m.