Triple
T29654811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragoon |
E750236
|
entity |
| Predicate | attackName |
P167551
|
FINISHED |
| Object | Phase Disruptor |
—
|
NE NERFINISHED |
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: Phase Disruptor | Statement: [Dragoon, attackName, Phase Disruptor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attackName Context triple: [Dragoon, attackName, Phase Disruptor]
-
A.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
B.
attackEffect
Indicates that one entity’s attack produces a specific effect or consequence on another entity.
-
C.
offensiveSkill
Indicates a relationship where an entity possesses or demonstrates the ability to perform actions aimed at attacking, scoring, or otherwise advancing an offensive objective.
-
D.
notableAttack
Indicates that an entity carried out, was involved in, or is strongly associated with a particularly significant or well-known attack.
-
E.
attacks
Indicates that one entity initiates an aggressive or harmful action directed toward another entity.
- F. None of above. chosen
Provenance (4 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f66f269b908190a8a5f65bac23f083 |
completed | May 2, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 6:54 p.m.