Triple
T37465284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metamorphosis |
E931018
|
entity |
| Predicate | effectDetail |
P196106
|
FINISHED |
| Object | Replace your Hero Power with ‘Deal 5 damage’ for 2 uses |
—
|
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: Replace your Hero Power with ‘Deal 5 damage’ for 2 uses | Statement: [Metamorphosis, effectDetail, Replace your Hero Power with ‘Deal 5 damage’ for 2 uses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectDetail Context triple: [Metamorphosis, effectDetail, Replace your Hero Power with ‘Deal 5 damage’ for 2 uses]
-
A.
effectDescription
chosen
Indicates a textual explanation of the outcome, consequence, or impact resulting from an action, event, or condition.
-
B.
effectCategory
Indicates the general type or classification of an effect that one entity has on another or on a system.
-
C.
effectCount
Indicates the number of distinct effects or outcomes associated with a given action, event, or entity.
-
D.
effectTrigger
Indicates that one event, condition, or action initiates or causes another effect to occur.
-
E.
ultimateEffect
Indicates the final or overall outcome that results from a preceding action, condition, or sequence of events.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
Created at: May 3, 2026, 4:17 p.m.