Triple
T13326269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CIWS |
E317448
|
entity |
| Predicate | counterMeasureAgainst |
P109536
|
FINISHED |
| Object | sea-skimming missiles |
—
|
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: sea-skimming missiles | Statement: [CIWS, counterMeasureAgainst, sea-skimming missiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: counterMeasureAgainst Context triple: [CIWS, counterMeasureAgainst, sea-skimming missiles]
-
A.
countermeasureCategory
Indicates the classification type or category to which a given countermeasure belongs.
-
B.
countermeasuresFaced
Indicates that one entity has encountered or had to deal with countermeasures implemented by another entity.
-
C.
counterplay
Indicates a responsive action or strategy taken to oppose, mitigate, or neutralize another party’s move or advantage.
-
D.
counterattackBy
Indicates that an entity launches a retaliatory attack in response to an initial attack carried out by another entity.
-
E.
controlMeasure
Indicates a relationship where one entity implements or applies a method, action, or mechanism to regulate, mitigate, or manage a risk, process, or condition associated with another entity.
- 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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6babd88190a5d529df9584b9a4 |
completed | April 11, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69d99cf7f9c48190a6a4f452b4a2aefa |
completed | April 11, 2026, 12:59 a.m. |
Created at: April 9, 2026, 9:30 p.m.