Triple
T38620496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mutalisk |
E936852
|
entity |
| Predicate | attackProperty |
P4333
|
FINISHED |
| Object | bouncing attack |
—
|
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: bouncing attack | Statement: [Mutalisk, attackProperty, bouncing attack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attackProperty Context triple: [Mutalisk, attackProperty, bouncing attack]
-
A.
attackType
chosen
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
B.
attackValue
Indicates the offensive strength or damage potential an entity can inflict in an interaction or combat scenario.
-
C.
attackProfile
Indicates a relationship where one entity initiates or carries out an aggressive or hostile action against another entity.
-
D.
attackEffect
Indicates that one entity’s attack produces a specific effect or consequence on another entity.
-
E.
attackContext
Indicates the situational circumstances, conditions, or factors surrounding an attack event or action.
- 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_69f76ed403208190b862dc795171353f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: May 3, 2026, 4:32 p.m.