Triple
T7187626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fire Flower |
E167609
|
entity |
| Predicate | primaryAttack |
P4333
|
FINISHED |
| Object | fireball projectile |
—
|
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: fireball projectile | Statement: [Fire Flower, primaryAttack, fireball projectile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAttack Context triple: [Fire Flower, primaryAttack, fireball projectile]
-
A.
primaryDamageType
Indicates the main kind of harm or injury that an action, event, or object is responsible for causing.
-
B.
primaryEffect
Indicates the main direct outcome or consequence that results from a given cause, action, or condition.
-
C.
attackType
chosen
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
D.
primaryPower
Indicates that one entity serves as the main or dominant source of power or energy for another entity.
-
E.
mainAttacker
Indicates that an entity is the primary or leading aggressor responsible for initiating or carrying out an attack against 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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e8e2506881909fc4e81b9b79e873 |
completed | March 27, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69c6e752385c819096fbab55566ee2a8 |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:50 p.m.