Triple
T13119784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hammer Bro |
E311690
|
entity |
| Predicate | attackPattern |
P4333
|
FINISHED |
| Object | throws arcing hammers in volleys |
—
|
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: throws arcing hammers in volleys | Statement: [Hammer Bro, attackPattern, throws arcing hammers in volleys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attackPattern Context triple: [Hammer Bro, attackPattern, throws arcing hammers in volleys]
-
A.
attackType
chosen
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
B.
attackProfile
Indicates a relationship where one entity initiates or carries out an aggressive or hostile action against another entity.
-
C.
attackEffect
Indicates that one entity’s attack produces a specific effect or consequence on another entity.
-
D.
attacks
Indicates that one entity initiates an aggressive or harmful action directed toward another entity.
-
E.
attackOccurred
Indicates that an act of aggression or violence was carried out by one party against another.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98196e69081909111407ee3d9f08e |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98043a74c81908648e6cd0b4c7f71 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:06 p.m.