Triple
T26502544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nike Missile Site SF-88 |
E669458
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nike missile site |
C16080
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Nike missile site Context triple: [Nike Missile Site SF-88, instanceOf, Nike missile site]
-
A.
Cold War military site
chosen
A Cold War military site is a strategically located facility, installation, or complex developed or used during the Cold War era for defense, surveillance, weapons deployment, command and control, or related military operations shaped by nuclear deterrence and superpower rivalry.
-
B.
missile command
Missile command is a strategic control system responsible for detecting incoming threats and coordinating the launch, guidance, and interception of missiles to defend designated assets.
-
C.
NASA rocket engine test facility
A NASA rocket engine test facility is a specialized complex equipped with infrastructure, instrumentation, and safety systems to ground-test and validate rocket engines under controlled, flight-like conditions.
-
D.
U.S. Air Force missile
A U.S. Air Force missile is a guided weapon system designed, operated, or managed by the United States Air Force for offensive or defensive military purposes, including strategic deterrence, precision strike, and air or missile defense missions.
-
E.
gunpowder magazine complex
A gunpowder magazine complex is a secured facility composed of specialized storage buildings and supporting structures designed to safely house, handle, and protect large quantities of gunpowder or explosives.
- F. None of above.
Provenance (1 batch)
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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
Created at: April 27, 2026, 1:14 a.m.