Triple
T22020710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drone Mimic |
E543836
|
entity |
| Predicate | attackStyle |
P4333
|
FINISHED |
| Object | close-range surprise 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: close-range surprise attack | Statement: [Drone Mimic, attackStyle, close-range surprise attack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attackStyle Context triple: [Drone Mimic, attackStyle, close-range surprise attack]
-
A.
attackType
chosen
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
B.
combatStyleAgainst
Indicates the specific way or method one entity uses to fight or engage in combat when facing another entity.
-
C.
attackEffect
Indicates that one entity’s attack produces a specific effect or consequence on another entity.
-
D.
strikeAction
Indicates an action where one entity forcefully hits, attacks, or impacts another entity.
-
E.
打撃スタイル
Indicates a relationship where an entity is characterized by or associated with a particular style or manner of striking or hitting.
- 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_69e11e2e8ea4819084210fe06d3a1b8d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127c7b3308190ac056bef6f82722e |
completed | April 28, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:23 p.m.