Triple
T37459303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toshley |
E930877
|
entity |
| Predicate | deathrattleEffect |
P189106
|
FINISHED |
| Object | Add a Spare Part card to your hand |
—
|
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: Add a Spare Part card to your hand | Statement: [Toshley, deathrattleEffect, Add a Spare Part card to your hand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathrattleEffect Context triple: [Toshley, deathrattleEffect, Add a Spare Part card to your hand]
-
A.
effectOfDeath
Indicates the causal impact or consequences that a death has on another entity, state, or process.
-
B.
deathRite
Indicates a ritual, ceremony, or set of practices performed in connection with someone's death or burial.
-
C.
deathTriggers
Indicates that the occurrence of one entity’s death causes or initiates another event, state, or process.
-
D.
dropsOnDeath
chosen
Indicates that when an entity dies, it releases or leaves behind a specified item or set of items.
-
E.
damageEffect
Indicates that one entity causes harm, reduction, or deterioration to another entity or its properties.
- 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_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:17 p.m.