Triple
T29654967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Immortal |
E750239
|
entity |
| Predicate | BarrierEffect |
P85838
|
FINISHED |
| Object | absorbs incoming damage |
—
|
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: absorbs incoming damage | Statement: [Immortal, BarrierEffect, absorbs incoming damage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BarrierEffect Context triple: [Immortal, BarrierEffect, absorbs incoming damage]
-
A.
attackEffect
Indicates that one entity’s attack produces a specific effect or consequence on another entity.
-
B.
tierEffect
Indicates how belonging to a particular tier influences or modifies the outcome, behavior, or properties associated with that tier.
-
C.
isBarrierTo
chosen
Indicates that one entity obstructs, prevents, or significantly hinders another entity from occurring, progressing, or being accessed.
-
D.
hasDifficultyEffect
Indicates that one entity causes a change in the difficulty level or challenge associated with another entity or activity.
-
E.
tailAttackEffect
Indicates an effect that occurs when an entity performs an attack using its tail.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f66f274ba08190bcdbdfeccf4af09d |
completed | May 2, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:54 p.m.