Triple
T20507605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malmstrom Air Force Base |
E503473
|
entity |
| Predicate | hasStrategicDeterrenceMission |
P4900
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Malmstrom Air Force Base, hasStrategicDeterrenceMission, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStrategicDeterrenceMission Context triple: [Malmstrom Air Force Base, hasStrategicDeterrenceMission, true]
-
A.
isStrategicWeapon
Indicates that the weapon is designed or classified for large-scale, long-range, or high-impact strategic use rather than for tactical or localized operations.
-
B.
nuclearCapability
Indicates that an entity possesses, develops, or has access to nuclear weapons or the technological capacity to produce them.
-
C.
hasNuclearRole
chosen
Indicates that an entity participates in, is responsible for, or holds authority related to nuclear activities, functions, or capabilities.
-
D.
missileLaunchCapability
Indicates that an entity has the ability or functionality to launch missiles.
-
E.
hasNuclearWeapons
Indicates that the subject possesses or controls nuclear weapons.
- 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_69e0b4b1e52c8190894281cf7e3283ab |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69dc8f3c881908ed2e0257a057e73 |
completed | April 20, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:36 a.m.