Triple
T35780741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Close-In Weapon System |
E1034429
|
entity |
| Predicate | isIntendedToCounter |
P46826
|
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: [Close-In Weapon System, isIntendedToCounter, sea-skimming missiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIntendedToCounter Context triple: [Close-In Weapon System, isIntendedToCounter, sea-skimming missiles]
-
A.
intendsTo
Indicates that one entity has the purpose, plan, or desire to perform an action involving another entity or outcome.
-
B.
intendedWith
Indicates that one entity is the planned or desired target, recipient, or context for the use or application of another entity.
-
C.
isSupposedToBe
Indicates that something is expected or intended to have a particular state, quality, or role, whether or not it actually does.
-
D.
hasIntendedEffect
chosen
Indicates that one entity is expected or designed to produce a particular effect or outcome on another entity or context.
-
E.
isIntendedToSupport
Indicates that one entity is designed or purposed to provide assistance, reinforcement, or backing to another entity or activity.
- 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_69f76e14a1e081908eddd57bd6fdb3be |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.