Triple
T20339265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secret Communication System |
E495695
|
entity |
| Predicate | aimedToCounter |
P109536
|
FINISHED |
| Object | enemy jamming |
—
|
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: enemy jamming | Statement: [Secret Communication System, aimedToCounter, enemy jamming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimedToCounter Context triple: [Secret Communication System, aimedToCounter, enemy jamming]
-
A.
counterattackBy
Indicates that an entity launches a retaliatory attack in response to an initial attack carried out by another entity.
-
B.
counterMeasureAgainst
chosen
Indicates a relationship where one entity serves as a response or defensive action intended to prevent, mitigate, or neutralize the effects of another entity.
-
C.
counterplay
Indicates a responsive action or strategy taken to oppose, mitigate, or neutralize another party’s move or advantage.
-
D.
aimsToCapture
Indicates an intention or effort by one entity to take control of, seize, or gain possession of another entity.
-
E.
aimOfAttacker
Indicates that a particular goal, target, or objective is what the attacker intends to achieve or affect.
- 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_69e0b4a1a09881908d97270d6971a25a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e678342a0081908ede8006eb5506a3 |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:23 a.m.