Triple
T12922771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FASGW(H) anti-ship missiles |
E309164
|
entity |
| Predicate | killChainRole |
P107032
|
FINISHED |
| Object | terminal strike weapon |
—
|
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: terminal strike weapon | Statement: [FASGW(H) anti-ship missiles, killChainRole, terminal strike weapon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: killChainRole Context triple: [FASGW(H) anti-ship missiles, killChainRole, terminal strike weapon]
-
A.
roleInSabotage
Indicates that an entity participated in or had a specific role in an act of sabotage.
-
B.
successorStateRole
Indicates that one role represents the state or position that directly follows and replaces another role in a sequence or process.
-
C.
roleInCrime
Indicates the specific function, responsibility, or participation an entity has within the commission of a particular crime.
-
D.
describedTactic
Indicates that one entity has provided an explanation or account of a particular tactic used or proposed by another entity.
-
E.
securityApparatusRole
Indicates the role or function an entity holds within a security or law-enforcement apparatus.
- 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971e9576c81908eb59569af6da877 |
completed | April 10, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69d96fa9b7708190a9e9fa30f59ff580 |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d9708a86bc8190bcdcf97e845bb413 |
completed | April 10, 2026, 9:50 p.m. |
Created at: April 9, 2026, 5:42 p.m.