Triple
T31040874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS-18 Mod 4 |
E790989
|
entity |
| Predicate | designedToPenetrate |
P47072
|
FINISHED |
| Object | ballistic missile defenses |
—
|
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: ballistic missile defenses | Statement: [SS-18 Mod 4, designedToPenetrate, ballistic missile defenses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedToPenetrate Context triple: [SS-18 Mod 4, designedToPenetrate, ballistic missile defenses]
-
A.
designedToDefeat
chosen
Indicates that one entity is intentionally created or configured with the purpose of overcoming, neutralizing, or rendering ineffective another entity.
-
B.
designedToBomb
Indicates that something was intentionally created or configured for the purpose of bombing a target.
-
C.
designedToWithstand
Indicates that something has been intentionally created or engineered to resist, endure, or remain functional under specified conditions, forces, or stresses.
-
D.
يخترقها
Indicates that an entity penetrates, passes through, or breaches another entity.
-
E.
canInfiltrate
Indicates that one entity has the ability or potential to secretly enter, penetrate, or gain access to another entity or system, typically without detection.
- 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: April 29, 2026, 8:59 p.m.