Triple
T37463384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volcanosaur |
E930974
|
entity |
| Predicate | hasBattlecryEffect |
P195330
|
FINISHED |
| Object | Double Adapt |
—
|
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: Double Adapt | Statement: [Volcanosaur, hasBattlecryEffect, Double Adapt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBattlecryEffect Context triple: [Volcanosaur, hasBattlecryEffect, Double Adapt]
-
A.
hasBattlecry
chosen
Indicates that an entity possesses or is associated with a specific battlecry, typically a shouted phrase or sound used at the onset of combat or action.
-
B.
hasHeroPower
Indicates that one entity possesses or is endowed with a special ability or power characteristic of a hero in relation to another entity.
-
C.
summoningSickness
Indicates that an entity is temporarily unable to act or perform certain actions immediately after entering the field or coming under a player’s control.
-
D.
hasBurstDamagePotential
Indicates the extent to which an entity can inflict a large amount of damage in a short, concentrated period of time.
-
E.
summonedMinionKeyword
Indicates that one entity has been brought into play or created as a subordinate or controlled minion by another entity.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
Created at: May 3, 2026, 4:17 p.m.