Triple
T9726290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS-17 Spanker |
E235619
|
entity |
| Predicate | nuclearTriadComponent |
P47242
|
FINISHED |
| Object | land-based ICBM leg |
—
|
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: land-based ICBM leg | Statement: [SS-17 Spanker, nuclearTriadComponent, land-based ICBM leg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nuclearTriadComponent Context triple: [SS-17 Spanker, nuclearTriadComponent, land-based ICBM leg]
-
A.
nuclearCapability
Indicates that an entity possesses, develops, or has access to nuclear weapons or the technological capacity to produce them.
-
B.
nuclearWarheadCarrier
chosen
Indicates that an entity is designed or used to carry, transport, or deliver nuclear warheads.
-
C.
hasNATOCompatibleSystems
Indicates that an entity possesses systems or equipment that are compatible with NATO standards and can interoperate with NATO forces.
-
D.
nuclearWeaponsProgram
Indicates the existence, development, or pursuit of a program related to the research, production, or maintenance of nuclear weapons.
-
E.
nuclearPowered
Indicates that something operates using nuclear energy as its primary power source.
- 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_69ca84d0fad481909cdd45aa77416c48 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9e798c348190885b79d7dffc9d8d |
completed | April 1, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69cd03c6ffc88190a5e9569e19122ad5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:21 p.m.