Triple
T18959316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alaskan NORAD Region |
E463867
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | component of NORAD |
C41465
|
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: component of NORAD Context triple: [Alaskan NORAD Region, instanceOf, component of NORAD]
-
A.
Canadian NORAD Region
The Canadian NORAD Region is the division of the North American Aerospace Defense Command responsible for aerospace warning, control, and defense operations over Canadian territory and adjacent airspace.
-
B.
Air and Space Operations Center
An Air and Space Operations Center is a command and control facility that plans, directs, coordinates, and monitors air and space operations to achieve assigned military objectives.
-
C.
component of NATO command structure
A component of NATO command structure is an organizational entity—such as a headquarters, command, or specialized unit—responsible for planning, directing, and coordinating specific military or strategic functions within the Alliance’s integrated chain of command.
-
D.
National Defense Management Center
The National Defense Management Center is a centralized command and control facility responsible for coordinating, monitoring, and directing a nation's military and defense operations at the strategic level.
-
E.
component of the Defense Intelligence Agency
A component of the Defense Intelligence Agency is an organizational unit within the DIA that performs specialized intelligence, analytic, operational, or support functions in alignment with the agency’s defense and national security mission.
- F. None of above. chosen
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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, noon