Triple
T37540672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hallazeal the Ascended |
E933316
|
entity |
| Predicate | damageSourceForEffect |
P186806
|
FINISHED |
| Object | your spells |
—
|
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: your spells | Statement: [Hallazeal the Ascended, damageSourceForEffect, your spells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: damageSourceForEffect Context triple: [Hallazeal the Ascended, damageSourceForEffect, your spells]
-
A.
damageSource
chosen
Indicates the origin or cause responsible for inflicting damage in an event or interaction.
-
B.
damageEffect
Indicates that one entity causes harm, reduction, or deterioration to another entity or its properties.
-
C.
hasStatusEffectSource
Indicates that a status effect currently applied to an entity originates from, or was caused by, a specific source entity or event.
-
D.
damageBasis
Indicates the underlying reason, cause, or basis on which damage is determined or assessed in a given context.
-
E.
damageLeadsTo
Indicates that one instance of damage causally results in or contributes to another specified outcome or condition.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:17 p.m.