Triple
T37515111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Templar |
E932613
|
entity |
| Predicate | supportsDamageType |
—
|
GENERATED |
| Object | elemental damage |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDamageType Context triple: [Templar, supportsDamageType, elemental damage]
-
A.
coversDamageType
chosen
Indicates that one entity provides protection, compensation, or applicability for a specified type of damage.
-
B.
hasTypeOfDamage
Indicates that an entity experiences or exhibits a specific kind or category of damage.
-
C.
cannotBeDamagedBy
Indicates that one entity is immune to harm, injury, or degradation caused by another specified entity or factor.
-
D.
damageTo
Indicates a relationship where one entity causes harm, loss, or deterioration to another entity.
-
E.
damageBasis
Indicates the underlying reason, cause, or basis on which damage is determined or assessed in a given context.
- F. None of above.
Provenance (1 batch)
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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.