Triple
T639538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strategic Defense Initiative |
E16701
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States defense program |
C368
|
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: United States defense program Context triple: [Strategic Defense Initiative, instanceOf, United States defense program]
-
A.
U.S. Department of Defense strategic document
A U.S. Department of Defense strategic document is an official, high-level publication that outlines long-term defense objectives, priorities, and plans for employing military resources to protect national security interests.
-
B.
nuclear weapons program
A nuclear weapons program is an organized, often state-led effort to research, develop, test, produce, and maintain nuclear warheads and their delivery systems for military deterrence or potential use.
-
C.
United States government program
chosen
A United States government program is an organized set of activities, services, or regulations funded and administered by federal agencies to achieve specific public policy goals or address national needs.
-
D.
defense organization
A defense organization is an entity, typically governmental or intergovernmental, responsible for planning, coordinating, and executing activities to protect a nation or group of nations from military and security threats.
-
E.
NATO military position
A NATO military position is a standardized role or appointment within the North Atlantic Treaty Organization’s integrated command or force structure, defining specific responsibilities, rank equivalencies, and functions across member nations’ armed forces.
- 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:35 p.m.