Triple
T37455757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Destroyer |
E930794
|
entity |
| Predicate | notableAbilityType |
—
|
GENERATED |
| Object | area-of-effect melee attacks |
—
|
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: notableAbilityType Context triple: [Destroyer, notableAbilityType, area-of-effect melee attacks]
-
A.
notableFeat
Indicates that an entity is recognized for having achieved or performed a particularly significant or distinguished feat.
-
B.
notablePower
Indicates that an entity possesses a significant or distinguished form of power, influence, or capability that is recognized as noteworthy.
-
C.
notablePowerType
chosen
Indicates that an entity is especially known for possessing or using a particular type of power or ability.
-
D.
notableTraitOnStage
Indicates that an entity is characterized by a distinctive or noteworthy trait specifically in the context of performing or appearing on stage.
-
E.
hasCharacterAbility
Indicates that a character possesses or can perform a specific ability.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.