Triple
T37459617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malorne |
E930884
|
entity |
| Predicate | hasDeathrattle |
P200676
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Malorne, hasDeathrattle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeathrattle Context triple: [Malorne, hasDeathrattle, true]
-
A.
hasBattlecry
Indicates that an entity possesses or is associated with a specific battlecry, typically a shouted phrase or sound used at the onset of combat or action.
-
B.
effectOfDeath
Indicates the causal impact or consequences that a death has on another entity, state, or process.
-
C.
hasHeroPower
Indicates that one entity possesses or is endowed with a special ability or power characteristic of a hero in relation to another entity.
-
D.
canRaiseUndeadMinions
Indicates the ability of an entity to animate and control undead creatures as subordinate minions.
-
E.
summoningSickness
Indicates that an entity is temporarily unable to act or perform certain actions immediately after entering the field or coming under a player’s control.
- F. None of above. chosen
Provenance (4 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_69ff9e91bba08190af04b31ad815b13a |
completed | May 9, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69ff9e00e4808190bde8f07e6519a72c |
completed | May 9, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69ff9e90b5248190bdd8d13f966b63e1 |
completed | May 9, 2026, 8:52 p.m. |
Created at: May 3, 2026, 4:17 p.m.