Triple
T31223407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Cyber Force |
E796073
|
entity |
| Predicate | usesCapabilityType |
P55904
|
FINISHED |
| Object | computer network 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: computer network attack | Statement: [National Cyber Force, usesCapabilityType, computer network attack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCapabilityType Context triple: [National Cyber Force, usesCapabilityType, computer network attack]
-
A.
usesCapabilityModel
Indicates that one entity employs or relies on a specific capability model to perform its functions or make decisions.
-
B.
usedCapability
Indicates that an entity employed or exercised a particular capability, skill, or function in performing an action or achieving a result.
-
C.
capabilityType
chosen
Indicates the type or category of capability that an entity possesses or is associated with.
-
D.
hasCapType
Indicates that an entity possesses or is characterized by a specific type of cap or cap-like feature.
-
E.
requiresCapability
Indicates that one entity depends on another entity possessing a specific capability in order for an action, function, or condition to be fulfilled.
- 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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: April 29, 2026, 9:10 p.m.