Triple
T11929964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henschel Hs 293 |
E283883
|
entity |
| Predicate | guidanceVulnerability |
P56378
|
FINISHED |
| Object | susceptible to Allied 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: susceptible to Allied jamming | Statement: [Henschel Hs 293, guidanceVulnerability, susceptible to Allied jamming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guidanceVulnerability Context triple: [Henschel Hs 293, guidanceVulnerability, susceptible to Allied jamming]
-
A.
securityAdvisory
Indicates a relationship where an entity issues, references, or is associated with a warning or guidance about security vulnerabilities, risks, or protective measures.
-
B.
vulnerabilityType
chosen
Indicates the specific kind or category of vulnerability associated with an entity or situation.
-
C.
strategicVulnerability
Indicates a relationship where an entity is exposed to potential harm or disadvantage in a way that can be deliberately exploited within a strategic or competitive context.
-
D.
associatedWithVulnerability
Indicates a relationship where an entity is linked to, affected by, or relevant to a specific vulnerability or security weakness.
-
E.
securityRecommendation
Indicates that one entity advises or prescribes specific security-related actions, settings, or measures for another entity.
- 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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90303a9a88190a4044e6310ba9b4b |
completed | April 10, 2026, 2:02 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3af0188190bfb22be5c97b3349 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.