Triple
T36958264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pain Elemental |
E914241
|
entity |
| Predicate | killEffect |
P27814
|
FINISHED |
| Object | prevents further Lost Soul spawning upon death |
—
|
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: prevents further Lost Soul spawning upon death | Statement: [Pain Elemental, killEffect, prevents further Lost Soul spawning upon death]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: killEffect Context triple: [Pain Elemental, killEffect, prevents further Lost Soul spawning upon death]
-
A.
killMechanism
Indicates the method or process by which one entity causes the death or destruction of another.
-
B.
effectOfDeath
chosen
Indicates the causal impact or consequences that a death has on another entity, state, or process.
-
C.
damageEffect
Indicates that one entity causes harm, reduction, or deterioration to another entity or its properties.
-
D.
attackEffect
Indicates that one entity’s attack produces a specific effect or consequence on another entity.
-
E.
willKill
Indicates that one entity is destined or intends to cause the death of another entity in the future.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.