Triple
T9594225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea Gnat decoy system |
E231489
|
entity |
| Predicate | intendedEffectOnThreat |
P46826
|
FINISHED |
| Object | break missile lock |
—
|
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: break missile lock | Statement: [Sea Gnat decoy system, intendedEffectOnThreat, break missile lock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedEffectOnThreat Context triple: [Sea Gnat decoy system, intendedEffectOnThreat, break missile lock]
-
A.
recognizesThreat
Indicates that an entity identifies or acknowledges another entity or situation as a potential danger or source of harm.
-
B.
primaryAdversaryCapabilityCountered
Indicates that a primary adversary capability is neutralized, mitigated, or otherwise rendered ineffective by a specified countermeasure or action.
-
C.
hasIntendedEffect
chosen
Indicates that one entity is expected or designed to produce a particular effect or outcome on another entity or context.
-
D.
threatTypeAddressed
Indicates that a given action, measure, or entity is specifically intended to counter or mitigate a particular type of threat.
-
E.
threatenedBy
Indicates that one entity poses a danger or potential harm to 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_69ca8482884481908eccdfdf64d6fbf7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a134b0c81908a568e5d2ecfbb92 |
completed | April 1, 2026, 10:20 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a359788190b24f82399489f7fe |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:07 p.m.