Triple
T37457057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secret Mage |
E930825
|
entity |
| Predicate | disruptionTool |
P28572
|
FINISHED |
| Object | Counterspell |
—
|
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: Counterspell | Statement: [Secret Mage, disruptionTool, Counterspell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disruptionTool Context triple: [Secret Mage, disruptionTool, Counterspell]
-
A.
disruptedIn
Indicates that a normal process, function, or state is interrupted, impaired, or thrown into disorder within the specified context.
-
B.
disruptsContinuityOf
Indicates that one entity interrupts, breaks, or otherwise prevents the ongoing, uninterrupted progression or sequence of another entity or process.
-
C.
ageOfDisruption
Indicates a temporal relationship specifying the period or point in time during which a disruption occurs or is in effect.
-
D.
attackToolExample
Indicates that a specific tool or method is used as an example of how an attack is or can be carried out.
-
E.
toolIn
chosen
Indicates that one entity is a tool or instrument used in or associated with another entity or context.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.